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.
In Microsoft’s Developer Preview – March Update, you’ll learn about static code analysis, help for new pages, creating role center headlines, an improved experience for event subscribers, choosing the cue layout on role centers, and inspecting contents of tables.
The Visual Studio Code Marketplace is offering a CRS AL Language Extension. Definitely a “must-have” for AL developers!
Adrian reports, “I have multiple versions of NAV (2009 classic-2018) installed on my local machine and was having an issue with opening the session page and debugger for all versions except NAV 2018. I finally find the solution from the Debugging Dynamics NAV in a side-by-side installation post on Dynamics User Group. Not sure whether there are other solutions, but this one works and I just wanted to share.”
Kyle asks, “Have any of you had problems restoring a NAVDATA backup where it fills up your disk? I have a single NAV company, exported from a customer that resulted in an uncompressed NAVDATA file that is about one GB. NAV 2017.
When I attempted to restore it on my local system, not only did it make the database explode to 50 GB, it also made the txlog grow to 30 GB, and it was still only 50% complete. It filled up my disk.
Has anybody else had that problem? I've also had the same issue with NAV 2015.”
Bill suggests, “Maybe the file autogrowth settings are causing the issue? Change from a percent to a fixed size. You could also try putting the dB recovery mode to simple during the restore.”
Kyle adds, “I already had it set to simple. And if I turn off autogrowth that just makes the restore die that much sooner (when it hits that wall, as opposed to when it fills up my disk). The problem is that restoring one GB should not need to consume 75 GB of database and log file space.”
He also notes, “I tried the same exact NAVDATA restore against SQL Express 2014, and it does not have the problem. So it must be something related to my SQL 2017. I have also confirmed that it doesn't matter whether I do the restore in RTC or PowerShell. I let it run for 14 hours and it never completed. Nothing useful in the SQL log. It consumed 160GB of database space before it just stopped working.”
Bill quips, “Did you try 15 hours? ;) It'd be interesting to see what's going on with a SQL trace. Have you tried the latest SQL 2017 CU? Maybe try the SQL Docker image to see if it is something environment related. What that might be though…”
If any of you have had a similar issue or know of a solution, please comment below.
If you are interested in NAV development, be sure to see our collection of NAV Development Blogs.
Read the "How To" blogs from ArcherPoint for practical advice on using Microsoft Dynamics NAV.