ARCHIVED: In SSRS, how do I include action parameters to subreports?

Moving reports from the development instance to production can cause issues with action parameters to Report Builder subreports. In such cases, it would not be appropriate to set the expressions within the report to point to the full URL report path, which would hard-code the development site instance of the subreport.

For example, a report might include a map wherein each country or state represents a portion of a dataset, and is defined by polygon space enabling click-through functionality to a subreport. If the report pointed to the full path of a subreport it would look something like:

 https://sharepoint/sites/dev/BI_Centers/IU-POC/Report Library/IU-POC/Geographical/GeographicalUSStates.rdl

However, when this report moves from its development site to its test site, the hard-coded URL will continue to point to subreports that exist on the development server.

Instead of using the full path, it is more efficient to identify the highest level of the report library in the site where the reports reside, and then remove all URL information up to the library:

 /Report Library/IU-POC/Geographical/GeographicalUSStates.rdl

This allows the report to move from the development instance to the test instance, for example:

• Development instance:

   https://sharepoint/sites/dev/BI_Centers/IU-POC/Report Library/IU-POC/Geographical/GeographicalUSStates.rdl

• Test instance:

   https://sharepoint/sites/test/BI_Centers/IU-POC/Report Library/IU-POC/Geographical/GeographicalUSStates.rdl

The subreports will continue to work as expected and point to the instance intended after being moved. With a hard-coded URL, the test site report would point to subreports in the development instance.