There is no solution by Microsoft about this error when you run Report 10706 in a 2013R2 - Spanish localization?. All Customer has the same problem when run this report (standard, without changes) at the end of the year.
The solution is run with a "date filter" day by day? Is an anual report.
Anybody has the solution?
0
Answers
Franz Kalchmair, MVP
Alias: Jonathan Archer
please like / agree / verify my answer, if it was helpful for you. thx.
Blog: http://moxie4nav.wordpress.com/
Franz Kalchmair, MVP
Alias: Jonathan Archer
please like / agree / verify my answer, if it was helpful for you. thx.
Blog: http://moxie4nav.wordpress.com/
if theres a lot of aggregating going on you might wanna consider calculating values in C/AL instead of RDLC
http://forum.mibuso.com/discussion/46301/problem-with-a-report-with-many-pages
https://blogs.msdn.microsoft.com/nav/2014/03/09/rdlc-report-and-performance-in-microsoft-dynamics-nav/
try to reduce the printed data:
* only show really needed columns
* only show really needed rows (data)
you could also try following
create a codeunit
write in trigger onrun
report.savesasexcel(10706,filename) // or maybe try saveaspdf instead
run the cu directly or use job queue
Franz Kalchmair, MVP
Alias: Jonathan Archer
please like / agree / verify my answer, if it was helpful for you. thx.
Blog: http://moxie4nav.wordpress.com/
We have solved this run it on the server, but is very extrange that Microsoft don't review this, because is a standard Report.
This report analize all G/L Entry in a period (Normally, the customer filter for a year for audit) and lot of customers has the same problem. Partners are selling a solution with a hardware requirements (RAM,Processor,OS...) and then, with a standard report fails. What can we say to the Customer, you must buy more and more memory if you want to run this Report?
Franz Kalchmair, MVP
Alias: Jonathan Archer
please like / agree / verify my answer, if it was helpful for you. thx.
Blog: http://moxie4nav.wordpress.com/
Yes, We contacted with them and the answer was "If you want, we can optimize the Report" (If we pay, of course).
Obviously, we don't accept to pay for this, when the report is standard and isn't an especial requirement.
Is not a good support for the people who are selling their products.
I would add that another way to optimize the standard reports is to make use of the Report Label Designer and the Include Caption option on the column data data type lines.
Your goal is to send data like column headers and general report information only once, not with every line in the dataset.
For one of our client, they needed to print to PDF close to 1000 Sales Inv. reports at the same time. I basically removed all of the lines where the datasource ended in 'lbl' in the sales inv. line dataset and filled them in a more efficient way.
Check out tips 1 and 2 from this post:
https://blogs.msdn.microsoft.com/nav/2015/03/17/a-couple-of-rdlc-performance-optimization-tips/