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.
I’ve been wrestling with this one report for a long time, and finally figured out what to do but it was serendipitous .
Well I changed a parameter that depends on a previous one to be "Internal" – then everythig worked like I wanted! thanks
How does "Internal" differ from "Hidden" in SSRS?
Internal is not exposed and you cannot pass it to the report when calling with parameters from another one. Note it will not appear at the top where the user can change it.
Hidden means that it won’t show at the top of the page to allow the user to manually adjust it, but it can be passed to the report via call from another report.
I prefer to use hidden and have sensible defaults on them. In that way I can always override if I need to them when navigating between reports.
I would also look at this similar answer : What are the rules for using "Internal" parameters in SSRS. It shows a good use case for Internal parameters, which I’ve used on occasion too.