Friday, February 01, 2013 9:17 AM
We have developed a SSRS 2008 report split on 3 pages. On first page, we show a value X based on a division by another value Y that is obtained on second page through different summations. With that, we have the following scenario:
1. Report is generated on Reporting Server (or Visual Studio) and value X is not correct because it seems that value Y has not been obtained yet at this time
2. We continue on page 2 and we can see that value Y is now correctly obtained
3. We come back to page 1 and now we are able to see value X with expected value
¿Does it exist some option to force that all report data was obtained at the same time, with independency of number of pages? We know that we can obtain Y value on first page on a new hidden table, but is not an efficient option to calculate same information twice.
Friday, February 01, 2013 3:36 PM
i haven't tried it yet, but perhaps you can force the report to pull all data when you use another expression than SUM where all data would be needed. For example =Last(Field, "<DatasetName>") within a textbox. If it works you could make this text box invisible or find a better place for it.
Just an idea for now.
- Proposed As Answer by Charlie LiaoMicrosoft Contingent Staff, Moderator Monday, February 04, 2013 3:31 AM
Monday, February 04, 2013 3:31 AMModerator
In Reporting Services 2008 or higher, reports are now processed and rendered page by page as a report user interactively reads through a report. The amount of data on each page influences the rendering time for each page. The total number of pages is determined when a report is rendered. We cannot use the report items’ value in its’ previous page. So in you scenario, the value X is not correct when the report initially run, and the value X is correct when you go to page 2 and then back to one. As Tilo said, I am afraid we cannot force that all report data was obtained at the same time.
Hope this helps.
If you have any feedback on our support, please click here.
TechNet Community Support
Wednesday, February 06, 2013 4:44 PM
Thanks for all your suggestions here. Finally, we have decided to re-calculate value Y in a dataset existing on page 1 in order to avoid scenario described.