posted 12/17/2010 by JeffRush - Views: [1909]
I'm going to be making a concerted effort to blog more going into the new year, so I will begin doing small little posts when I come across something I think others might find useful.
The backstory:
We have several reporting projects to organize reporting across various functional areas of our product suite.
Today, I came across a situation where I wanted to use a report from a different project as a subreport.
The problem:
The drop down box for the report selection will only allow you to pick from report available with the active project.
The solution:
You can use a relative path.
Do I feel like an idiot for not knowing this? Yes. Hopefully I can help others feel less idiot-like by sharing this little piece of knowledge.
Hat tip to Stacia Misner (BLOG | Twitter) for helping me out.
Nice tip, thanks. You should also be able to add the desired report/subreport to your current project by right clicking on Reports, and choosing Add >> Existing Item and then browsing to your report. This might be confusing in some environments, so the relative path can also be very useful.
Hey Daniel.
Adding it to the project is the way we were doing it historically when we needed it but that pretty much ensured that any future updates to the logic/functionality of the report we were using would have to be done manually to every project it lived in. We have 3500 or so reports across 5 projects so, needless to say, that was not pretty.
This relative path revelation is definitely going to help ensure that we keep as up to date as possible.
Thanks for the comment!
Good post Jeff. Having a goal of blogging more is great! I look forward to keeping up with your posts. :)
This won't run in test mode right? As it would need to be deployed to the same server as the report in question.
Brian, great point.
Using the relative path will only work when actually running it on the report server, it will not function correctly in BIDS