Screen parameters mapping does not match the screen definition?

Proposed Screen parameters mapping does not match the screen definition?

  • Thursday, January 31, 2013 2:10 PM
     
     

    Hi,

    I have screen from which I call another screen using a data grid row item as link ("Show as link" and then select another screen as "Target screen" , and  then configure screen parameters).

    Everything work fine when I have only one optional paaramter for that another screen. But when I added another optional parameter in runtime I have error: "Screen parameters maping does not match the screen definition?" Only one parameter I send from first screen to target one..?


    • Edited by Yann DuranModerator Thursday, April 18, 2013 6:04 AM Fixed spelling mistake in the title
    •  

All Replies

  • Thursday, March 21, 2013 3:10 PM
     
     

    Hi,

    I know that this is and old post...but..I think that the problem is that the parameter is not of the same type.

    Regards, 


  • Thursday, March 21, 2013 4:15 PM
    Moderator
     
     Proposed

    A screen is only able to be used as a target screen for "Show As Link" if it has one, & only one, nullable integer parameter.

    This is by design. If you think about it, it makes sense. If you have more than the one parameter, how is LightSwitch supposed to know what values to pass for the parameters.

    If you call the screen in code yourself, then you can have as many parameters as you like. It's then your responsibility to pass the values to it.


    Yann - LightSwitch Central - Click here for FREE Themes, Controls, Types and Commands
     
    Please click "Mark as Answer" if a reply answers your question. Please click "Vote as Helpful" , if you find a reply helpful.
     
    By doing this you'll help others to find answers faster.

    • Proposed As Answer by Gabriel Marazzi Wednesday, April 17, 2013 7:31 PM
    •