October 26, 2011 at 9:30 am
Hi,
I've been trying to analyse why the same multi-value string parameter is rendering differently in different reports after converting both reports from VS 2005 to 2008.
The text values are separated by pipes - |A|B|C|etc - and displays exactly the same in text boxes for both reports.
However, the parameters field in the execution log table shows the parameters being rendered differently: -
Report1 - Portfolios=Fund1&Portfolios=Fund2&Portfolios=Fund3&...etc...
Report2 - |Fund1|Fund2|Fund3|etc...
Report1 will display the data correctly in Report Manager.
Report2 will only display any data when only very few values are selected from the drop-down list.
I'd like to find out if anyone else has seen this behaviour and has been able to solve it.
Ideally Report2 should render the same as Report1 but I don't know how to approach the problem anymore than I have; such as deleting the parameter and corresponding dataset, created a new report and that didn't work.
Thanks
October 26, 2011 at 9:33 am
Is 1 parameter a free edit textbox and the other one a multi-value list?
October 26, 2011 at 9:43 am
No, they are both multi-value. The parameter in Report2 was actually cloned from Report1 as we generally copy existing reports and amend to suit.
October 26, 2011 at 9:47 am
Can you confirm this behavior by firing up profiler?
I've never heard that we can even edit the separator so I have nothing else to offer here.
October 26, 2011 at 9:56 am
I've ran traces against both reports and the strings come through the same and I've ran the code in Mgt Studio and it returns the correct data for both reports. It's the rendering in Report Manager that I cannot guage what is happening.
When I select just a few values for Report2 it will happily return the correct data. When I select all the values in the list it does not return the sub report.
October 26, 2011 at 10:00 am
And it doesn't fail the same way for both reports?
Did you change the datasource for report #2?
October 26, 2011 at 10:08 am
No, Report1 returns fine when selecting all list values, Report2 fails.
The dataset has not changed.
October 26, 2011 at 10:12 am
Trevor Reid (10/26/2011)
No, Report1 returns fine when selecting all list values, Report2 fails.The dataset has not changed.
I'd start another trace.
Add the rowcount column
Add the events SQLStmtCompleted AND SP:StmtCompleted.
Run both reports and see where it differs.
If those match perfectly then you know the problem comes from another place (maybe wrong user input in the schedule???).
October 26, 2011 at 10:16 am
Cheers, I'll do that and report my findings later [tomorrow!]. :Whistling:
Viewing 9 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply