There is an option to create “Internal” parameters in SSRS:
- In what context are they used?
- What are the general rules for using internal parameters?
There is an option to create Internal parameters in SSRS : In what context
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
There is an option to create “Internal” parameters in SSRS:
Internal Parameters in SSRS are parameters that are not configurable by the end-user at run-time.
This varies from a Hidden Parameter, which the user is not prompted to provide, but can still be configured through the URL to the report server.
Please see “Creating Report Parameters” on MSDN for more information.
One possible usage of them is in conjunction with the Report Viewer control. An ASP.Net page can contain the report viewer control, and use internal parameters in the code-behind to provide values to the report that the end-user should not be able to control, such as a UserID.
This can prevent the user from providing a different user’s ID in order to see data that they shouldn’t be allowed to view.
However, if you use an internal parameter in a report but want it to remain functional outside of the report viewer control, you’ll want to specify an appropriate default value. Otherwise the report will be unusable from the Report Manager or Report Server.