Store first parameter value in ssrs

  • Hi,

    I want to store the first value of a parameter entry by user.

    The parameter value will change each time and all I want to do is to capture the first initial value and show in report. The parameter value is an user entry.

    I tried storing the parameter value as read only variable and didn't work.

    Any suggestions on this is really appreciated.

  • I'm not sure I completely understand what your requirement is here, what do you mean my the value obtained by a parameter? Does your SP have a OUTPUT value that you want to return to your report? SSRS does not support these, you'd need to return the value in a dataset.

    If you then don't want that value to change if you then change certain values, you could then pass the value of your parameter into the SP as well (which is optional) and return the value of that parameter is it is not NULL, instead of doing your normal evaluation. Set the parameter as hidden, and then the user can't change its value.

    Thom~

    Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
    Larnu.uk

  • vigneshlagoons 51204 - Friday, July 7, 2017 7:51 AM

    Hi,

    I want to store the first value of a parameter entry by user.

    The parameter value will change each time and all I want to do is to capture the first initial value and show in report. The parameter value is an user entry.

    I tried storing the parameter value as read only variable and didn't work.

    Any suggestions on this is really appreciated.

    My interpretation of what you're looking for will require a new table, that has the user and the parameter value as fields, and only allows one record per user.   The stored procedure that feeds the report will then have to update that field in that table for that user as the first thing it does, and only if the existing value in that table is NULL.   That way, only the first run of the sproc from the report can successfully update that value.   However, that may also mean you need to capture the user information as a parameter, depending on how people are authenticating to SQL Server when they run a report.

    Steve (aka sgmunson) 🙂 🙂 🙂
    Rent Servers for Income (picks and shovels strategy)

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

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