This is a migrated thread and some comments may be shown as answers.

Navigate to Report

1 Answer 73 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Justin Lee
Top achievements
Rank 1
Justin Lee asked on 27 Sep 2013, 02:15 PM
I have a report that links (drills down) to other reports.  It actually has links to 10 other reports. 

I see 2 options for this: Navigate to an Object Instance, and Navigate to a Type name.

Object Instance:  The problem I'm running into with this is it creates an instance of each of the 10 reports. Some of the reports have code in the constructor that calls a web service that may or may not be there at design time. This causes the designer to crash (even though the code is wrapped in  if (!this.DesignMode))  My other concern is performance/memory issues since it creates these 10 reports at run time, instead of on-demand. (when link is clicked)

Type Name:  This option works well for us, except for the fact that the type name includes the assembly version, which gets updated every build (so we would have to constantly update the links).  This would not be maintainable without a script that searches for version numbers and updates them before each build. (which I'd rather not develop and maintain)

Any solutions to my scenario?


1 Answer, 1 is accepted

Sort by
0
Justin Lee
Top achievements
Rank 1
answered on 27 Sep 2013, 02:20 PM
It dawned on me right after posting...  I used Type Name, and after selecting the report, I just switched the version with a wildcard. i.e.   Version=* 
That appears to be working fine.
Tags
General Discussions
Asked by
Justin Lee
Top achievements
Rank 1
Answers by
Justin Lee
Top achievements
Rank 1
Share this question
or