ArcherPoint Dynamics NAV Developer Digest - vol 70
As they run into issues and questions, find the answers, and make new discoveries, they post them companywide on Yammer for everyone’s 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 group—so we thought, wouldn’t it be great to share them with the rest of the Microsoft Dynamics NAV Community? So, the ArcherPoint Microsoft Dynamics NAV Developer Digest was born. Each week, we present a collection of thoughts and findings from the ArcherPoint staff. We hope these insights will benefit you, too.
Saravanan Shanmugam shared this tip on handling a C/AL error:
If you face the attached error when you try to call any report object through C/AL(for example, ReportObejct.RUN), then you must set the UseRequestPage property to 'No’ in the called Report object.
The following C/AL functions are limited during write transactions because one or more tables will be locked. Form.RunModal is not allowed in write transactions. Codeunit.Run is allowed in write transactions only if the return value is not used. For example, ‘OK := Codeunit.Run()’ is not allowed. Report.RunModal is allowed in treansactions only if ‘RequestForm = FALSE’. For example, ‘Report.RunModal(…,FALSE)’ is allowed. XmlPort.RunModal is allowed in write transactions only if ‘RequestForm = FALSE’. For example, XmlPort.RunModal(…,FALSE)’ is allowed. Use the COMMIT function to save the changes before this call, or structure the code differently.
Saurav Dhyani shared an article on reducing the time required for performing NAV upgrades:
Data upgrade times sometimes exceed the allowed downtime for enterprises during an upgrade. There are several ways to handle this; this blog shows on way the author helped perform an upgrade from NAV 2009 R2 to NAV 2013 R2 in about 6 hours, an upgrade that normally would have taken over 78 hours.
From the article:
At the heart of the problem there was G/L Entry table. There are 11 companies in the database, and the largest one has 54 million records in the G/L Entry table, so it can’t really be fast. But what was the reason that the G/L Entry table was involved in the Step 1 of the upgrade procedure in the first place?
Read the entire article: How I Reduced Data Upgrade Time By 78 Hours
Saurav Dhyani also shared an article on how installing NAV 2016 overwrites the NAV 2015 Administration Tool:
From the article:
Dynamics NAV 2016 installs nicely side-by-side with Dynamics NAV 2015. There is one small issue with installing NAV 2016 along NAV 2015: the NAV Administration Tool of NAV 2015 doesn’t work anymore. If you start it, you will notice that the NAV 2015 Administration Tool is actually the NAV 2016 version. And you can’t administer the NAV 2015 servers using the NAV 2016 Administration Tool.
Read the entire article to find out more: NAV 2016 installation overwrites NAV 2015 Administration Tool.
If you are interested in NAV development, check out our collection of NAV Development Blogs.
For step-by-step instructions on how to perform specific tasks in Microsoft Dynamics NAV, see our collection of How-To blogs.
If you found this post useful, you might also be interested to read through our archive of the Dynamics NAV Developer Digest.