I'm getting an error that says "Invalid value of parameter "PersonID". This happened after an upgrade and the report no longer works.
It says to see the Inner Exception for details but doesn't provide a way to access it. We've recently re-created out data access layer, so there may have been a change we didn't see. Any ideas on how to access the inner exception so I can find a place to start looking?
It says to see the Inner Exception for details but doesn't provide a way to access it. We've recently re-created out data access layer, so there may have been a change we didn't see. Any ideas on how to access the inner exception so I can find a place to start looking?
2 Answers, 1 is accepted
0
Kennith
Top achievements
Rank 1
Rank 1
answered on 08 Apr 2010, 07:18 PM
Fixed. Turns out the value wasn't being filled and, for whatever reason, the report parameter did not allow nulls. Changing it to allow for nulls fixed the problem. I don't think the parameter is even used.. but it works.. so I'm shutting up :)
0
Hi Kennith,
The parameters handling has changed in the Q1 version - the parameters collection of the processing instance does not contain the values of the parameters, but is a dictionary of Parameter objects. The benefit is that from the Parameter object you may get not only the value of the parameter, but its Label as well (if the parameter has defined AvailableValues), type, etc. Same benefits are available when you use a parameter in an expression.
Also when the report enters the processing stage, report parameter values are validated against their validation properties (no matter if the parameter is visible or not). If one or more parameters do not have valid values, processing is aborted. The validation properties include the type of the parameter, is it a single or multi-value, is its value among the available values (if such are defined), is null value allowed etc. - more info in the Adding Parameters to Report help article.
The mandatory validation we've introduced in the Q1 is responsible for the exception you've received as it would be done even if the parameter is not used.
Hope this sheds more light on the matter.
Sincerely yours,
Steve
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
The parameters handling has changed in the Q1 version - the parameters collection of the processing instance does not contain the values of the parameters, but is a dictionary of Parameter objects. The benefit is that from the Parameter object you may get not only the value of the parameter, but its Label as well (if the parameter has defined AvailableValues), type, etc. Same benefits are available when you use a parameter in an expression.
Also when the report enters the processing stage, report parameter values are validated against their validation properties (no matter if the parameter is visible or not). If one or more parameters do not have valid values, processing is aborted. The validation properties include the type of the parameter, is it a single or multi-value, is its value among the available values (if such are defined), is null value allowed etc. - more info in the Adding Parameters to Report help article.
The mandatory validation we've introduced in the Q1 is responsible for the exception you've received as it would be done even if the parameter is not used.
Hope this sheds more light on the matter.
Sincerely yours,
Steve
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.