Wijmo / SSRS - Pass hidden parameter in initial request

Posted by: cbrown on 22 February 2018, 5:54 am EST

    • Post Options:
    • Link

    Posted 22 February 2018, 5:54 am EST

    I have a particular SSRS report that requires a hidden parameter to be passed before it will render. I’m not able to see anywhere in the wijmo documentation where I can set the array of parameters to send with the report request. Ideas?

  • Posted 22 February 2018, 3:37 pm EST

    Hi,

    You need to handle queryLoadingData event for ReportViewer to pass Report Parameter. Please refer to the attached sample for the same.

    ~Manish

    ReportViewer-SRSS_Parameterized.zip

  • Posted 23 February 2018, 3:13 am EST

    Thanks, Manish. I’ll take a look at the example.

  • Posted 23 February 2018, 4:15 am EST

    Hi Manish, I added the parameters

                e.data['parameters.forminstanceid'] = form.formInstanceId;
                e.data['parameters.subjectid'] = form.subjectId;
    

    I see the parameters being passed in the header of the request:

    	pageSettings.paginated:false
    	parameters.forminstanceid:40088
    	parameters.subjectid:26357
    

    But the report still seems to not be receiving the parameter, or at least it doesn’t appear that way. Is there anything on the api side I need to do to receive the parameters or should it automatically pick them up because they are named “parameters.xxxxxxxx” ?

    Thanks

  • Posted 23 February 2018, 4:27 am EST

    Please keep in mind, my original post indicated that this is a “hidden” parameter in the SSRS report.

  • Posted 23 February 2018, 4:35 am EST

    I just found that if I change the parameter to be “Visible” in SSRS, then the report runs, but this parameter cannot be visible because it contains just an internal ID for running the report. Any ideas on how to submit and execute a report that has hidden parameters?

  • Posted 25 February 2018, 8:11 pm EST

    Hi,

    We are working on this. We will update you soon.

    ~Manish

  • Posted 26 February 2018, 5:57 pm EST

    Hi,

    We are sorry for the inconvenience. We are able to replicate the issue at our end. This seems an issue with WebAPI. Hence, this issue has been forward to the concerned team for further investigation with tracking id 310863.

    We will let you know as we get any update on this.

    ~Manish

  • Posted 16 September 2018, 8:34 pm EST

    Hi,

    We are sorry for the delayed response on this.

    This issue has been fixed and included in the build 4.0.20182.128+. Please feel free to check.

    ~Manish

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels