December 29, 2014 at 2:34 pm
Hi,
Am running into a weird issue when subscribing a report. Its a data driven subscription and my proc returns a integer value (NULL in one case and some int value for other case). Based on this RDL selects one or multiple param values for report execution. i.e. when NULL, RDL pulls up all values and if an int, then it filters for that int value.
Now it works fine for when integer has some value. But when the value is passed a NULL (to pull all values), reporting services doesn't even attempt to run the rdl but instead throws error stating 'Default value or value provided for the report parameter 'id' is not a valid value'.
Am not sure what am i missing here?
December 29, 2014 at 4:59 pm
In Parameter Properties, do you have the "allow null value" box checked?
December 29, 2014 at 5:19 pm
Thanks for replying! Yes it does and the parameter data type is Int. One thing i left to update here is that the parameter's available values are filled up a T-SQL proc which has id-value as the result set and value is made available for user's display. This T-SQL proc returns NULL and a value to display for user.
Further to complicate, i replaced NULL with 0 on both T-SQL proc used for available values of param as well as the subscr proc that feeds this param with value. Still it throws the same error:doze:
December 29, 2014 at 10:19 pm
Figured out the problem was with the input parameter that was passed to the T-SQL proc which populates the available values. As incorrect param value was passed, the Reporting services executes it for available values and tried to validate it with the value that subscription proc feeds. As both are not matching, reporting services was throwing up this error.
I fixed the param passing for the T-SQL proc which fixed the issue.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply