ArcherPoint Dynamics NAV Developer Digest - vol 149
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.
Important Dynamics NAV Setting that Must be Changed
We should all be adjusting the MetadataProviderCacheSize in the CustomSetting.config file for every Dynamics NAV implementation from versions 2009 to NAV 2016. (**revised to version 2016 on 8/8/17 after Microsoft Dynamics NAV engineers pointed out to me that this setting is not being used in NAV 2017 and forward**). The default setting is 150, which means that the service tier is only caching 150 objects and then has to retrieve from the disk any new objects. At the default setting of 150 objects, NAV performance is really impacted. In the image I am working on I adjusted it to 3,000 so that almost all of the NAV objects are cached and the performance improved dramatically. With this I only see the performance issue the first time a particular object is called. It seems like this issue just never goes away and Microsoft has never adjusted the default to an acceptable number.
In this post by our friend Mark Brummel, Mark blows off some steam and imagines a world where customers are happy and resources are freed to take better care of them by moving to the latest and greatest release of Dynamic NAV. Upgrades really are easier than they’ve ever been.
Many of us are familiar with the iterative cycle of agile development and project management, but don’t often see it in our marketing teams. Microsoft took a new approach to fostering innovation within five teams, providing them with $10,000 each and 45 days to develop and test an innovative marketing idea, and it paid off.
In case you haven’t heard, there have been several rumblings of Paul White, long-time Dynamics SMB general manager, leaving Microsoft. See the MSDynamicsWorld article by Jason Gumpert for more information.
Every single time when you open the PowerShell ISE environment, you need to load Dynamics NAV modules. The function, “Import-NAVModules” figures out what you have installed on the system, and loads the module in the background.
You could include this script in your profile or create a module and load it automatically whenever you open the PowerShell ISE. If you are using VS Code for PowerShell, then creating a module is a way to go.
Installing MICR Fonts
If you have a MICR check for NAV 2017, you may wonder, “Where do I need to install the MICR font? Just the NST, or just the client system where RTC runs?” The answer is that the font needs to be on the machine that will be rendering the output.
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.