ArcherPoint Dynamics NAV Developer Digest - vol 141
The NAV community, including the ArcherPoint technical staff, is made up of developers, project managers, and consultants who are constantly communicating, with the common goal of sharing helpful information with one another to help customers be more successful.
As they run into issues and questions, find the answers, and make new discoveries, they post them on blogs, forums, social media...so everyone can benefit. We in Marketing watch these interactions and never cease to be amazed by the creativity, dedication, and brainpower we’re so fortunate to have in this community—so we thought, wouldn’t it be great to share this great information with everyone who might not have the time to check out the multitude of resources out there? So, the ArcherPoint Microsoft Dynamics NAV Developer Digest was born. Each week, we present a collection of thoughts and findings from NAV experts and devotees around the world. We hope these insights will benefit you, too.
End of Support Years for Dynamics NAV
In case you haven’t seen this in a while, the end of support by Microsoft for Dynamics NAV by year:
- 2018: NAV 2013 and NAV 2013 R2
- 2020: NAV 2015
- 2021: NAV 2016
- 2022: NAV 2017
Of course, many partners will continue to support older NAV versions beyond when Microsoft stops. Just know that the partners cannot get support from Microsoft on these versions after the posted year.
Dynamics NAV Developer Resources
Dynamics NAV Architecture Question – Reports
Assume you are working in a modern (2015 or newer) version of NAV, if I run a report that goes through a lot of data, something like an Inventory Valuation, where does the data have to go? Is it just between the SQL server and the NST? Or, does some or all of the dataset have to come to the RTC because that is where the report RDLC is being done?
Asked another way, if I am running the RTC far away from my NST, over a slow internet link, will that make my report run slower?
A1: The only data coming back to the client would be the resultant data set while 2-tier it would be any data coming back from SQL. This is why you'd see the 'out of memory' errors on older RCLC reports with really large data sets.
Yes, it could make it slower. Some options might include pairing the data set down and doing more processing NST side, via remote desktop or remoteapp.
A2: Agree. If it's NAV 2017, you might look at the new Task Scheduler feature where a report can be queued up by the user and delivered as PDF via e-mail. Another option is subscription-based SSRS, again where a PDF could be e-mailed.
A3: As I understand it, the resultant "dataset" is a compressed xml file. I don't think it would cause much of a problem unless your slow internet connection isn't even good enough to host RDP protocol. The out of memory errors for RDLC was from 2015 and older when RTC was 32-bit, if the uncompressed dataset was larger than ~1.7GB, it would crash, 2016 and 2017 have 64-bit RTC.
Response: This is 2016 so everything is 64 bit. The actual report that I'm having performance problems with winds up sending 200 pages of output. That is why I am concerned about the slow link between the RTC and the NST. I get that the actual dataset stays between the NST and SQL server, but that 200 pages has to move to the printer somehow.
Do you have anything to add to this conversation? Post in the comments below and we’ll keep you informed!
The Chick-fil-A way of Handling a Complaint: customer service at its best!
Acting Quickly Without Sacrificing Critical Thinking: another great blog from Harvard Business Review.
Stay abreast of what is new in the Microsoft Dynamics NAV community and at ArcherPoint by subscribing to our monthly newsletter, Better Business, by completing the form in our Resource Center.
And, if you are interested in NAV development, be sure to see our collection of NAV Development Blogs.