Large data set producing blank report

[sgrant776]

Hello,

My company is using Stimulsoft reports suite for dynamic reporting. Currently, we're using version 2015.3.0.0.
This has been fine until a customer reported receiving a blank report when selecting certain items. We typically restrict the dataset to 1000 rows but this time they selected a large subset. In testing this behavior, I ran a request for a report using 11,000 - 14,000 rows and successfully reproduced the behavior.

Long story short, our code seems to be working fine. The data is accurately queried and returned. However, the following 2 lines seem to be the problem:

Code: Select all

report.RegData("tableName",dtAD);
report.Dictionary.Synchronize();

When running the above with 1000 or less records, it's working just fine. Large subsets seem to be the problem.
I employed some google magic and surprisingly didn't find a lot of results for this. One issue seemed nearly identical and suggested the following properties on the aspx definition:

Code: Select all

ClientRequestTimeout="240"
CacheItemPriority="Normal"
ServerTimeout="00:30:00"

No result.
My initial guess would be that the version of Stimulsoft we're using is just running out of memory when trying to process this subset. But I'm not entirely sure as no errors are warnings are being thrown. Any assistance on this matter would be appreciated.


Lastly, while an upgrade to the latest version is absolutely possible, I would prefer to try and get this bug resolved by itself before embarking on that journey.
Initial efforts to upgrade have been... tedious, to say the least.

[Alex K.]

Hello,

Please send us a sample with test data which reproduces the issue for analysis.
Also, you can check the following articles to optimize your report (without an update on last release):
https://www.stimulsoft.com/en/blog/arti ... ng-reports
https://www.stimulsoft.com/en/blog/arti ... rts-part-2
https://www.stimulsoft.com/en/blog/arti ... rts-part-3

Thank you.

[sgrant776]

Hello,

I've looked over the links you posted.
I'll be doing a bit of back-end validation regarding querying and the returned dataset.
We're using this in a manner where the users can design their own custom reports to we're not able to impose such strict rules on a dynamic report. Trust me, we're trying to do what we can.
I've scrubbed and formed some test data that accurately reproduces the problem in our system. The sample size in the example document is only about 300 records less than what I actually tested with but still produces the problem.

Let me know if you need anything else.
Thank you.

[Alex K.]

Hello,

We couldn't reproduce this bug. Please try to check the last release.

Also, please clarify which viewer are you use?

Thank you.