ArcherPoint Dynamics NAV Developer Digest - vol 190
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.
Upgrading Data to Dynamics NAV 2018In Saurav’s blog, he walks us through each step required to upgrade data from previous versions of Dynamics NAV to NAV 2018, from preparing the old database to updating the web client, with notes and considerations for older versions of NAV.
What’s in a Name?For those of us that have been around NAV for a long time might be feeling a little nostalgic. Here’s a fun trip down Navision memory lane, from PC Plus to Business Central.
Error Messages When Importing New ObjectsSherry asks, “Hi all, recently at a client, when we import new objects, the users get an error message when trying to post a put away or inventory movement that the General Ledger Setup table has changed and it won't post. Our resolution is to compile the general ledger setup table and it works. Any reason why this would be happening? That table has not been modified for years.” Len responds, “Hi Sherry, I think it depends on the data you import. I'm not sure what version they are on, but a rule of thumb I always use is to import tables only when users are not in the system. Usually Codeunits or pages can be imported and they should be ok. When importing tables, you should always restart the NAV services after table imports. If you are not importing tables, let us know and we'll go from there. What version are they on?” Sherry, “Thanks Len! It is importing tables and forms, NAV 2016, not sure if services are being restarted.” Kyle chimes in, “Agree with Len. Anything 2015 or north is sensitive to having tables modified with users on. I always try to deploy off-hours, re-compile Menusuites (if modified), and restart service tiers. Often, the error users see is about a table that wasn't even changed. I never tried to find a pattern, I just release off-hours.”
Publishing Markdown Files from Git RepositoryDid you hear? You can now publish markdown files from a git repository to the VSTS Wiki. As you may be well aware, hosting pages such as readme, documentation, or SDK files can be problematic when hosted in code repositories. Check out Sandeep Chadda’s announcement showing exactly how to use it. 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.
- Login Error: Communication protocol mismatch between client and server
- Creating a Date Table in Power BI
- How to Make Measures Total Correctly in Power BI Tables
- The Microsoft Technology Stack – What It Is and Why You Should Care
- The Top Eight KPIs Retailers Should Be Tracking (with Formulas) for Your Retail KPI Dashboard