Post reply

Peculiar problem in Linked reports

  • March 22, 2007 at 2:18 am

    #119257

    Hi all ,

    I am encountering a peculiar problem while creating a linked report in SSRS.

    The scenario:

    My first reports contains 3 columns . The first 3 columns contain data from vendor table in AdventureWorks DB. They are VendorID , Name, CreditRating. The fourth column contains a link to the second report. It is just a link which jumps to the other report and passes the above three values as parameters to the second report.

    The second report contains 4 parameters which includes VendorID , Name, CreditRating and one more Postedby parameter which has to be entered manually when the second report is displayed. The three parameters from first report are passed on and one extra parameter has to entered manually then only the second report displays.

    It works fine when I check it on Visual Studio preview mode. I click the link for a particular row in First Report and it asks me to enter the Postedby Parameter. After entering it it displays the 2nd report. But the problem arises when I deploy it to report server. When I click the link on first report it throughs an error like " The Parameter 'PostedBy' is missing a value" whereas it should prompt the user to enter the PostedBy Parameter.

    I am stuck in this and not able to understand why this happens in ReportServer and not in Visual Studio Preview mode.

    Does anybody has any idea why this is happening ?

    Any Suggestion will be appreciated.

     

    Regards...

    Girija Shankar Beuria

  • March 24, 2007 at 9:44 am

    #696752

    Somebody Please help me in this. It's Urgent...

    Regards...

    Girija Shankar

  • March 28, 2007 at 4:22 pm

    #697550

    Not sure if you got this working, but make sure that parameters do in fact have data coming through.  Also, check the reportserver and make sure that the parameters are as expected.  Make sure that the PostedOn is set to prompt and not hidden.  You can try and check your parameters from your dataset is mapped to your parameters of the report.  Make sure that your parameters from the parent report are mapped to the child report when linking the reports. Try and test the child report by setting the posted date to "ALLOW NULL".  These are just suggestions.  If it works in Dev but not on production, make sure to double check the parameters on the reportserver for the report specified. 

     

    Thanks

    Greg

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply