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.
Gwen Brit shares:
Here's a little heads-up related to security and functionality. In version NAV 2017 (and only NAV 2017) there is a piece of code that updates the Customer or Vendor address on their Card if the address fields are blank and you enter an address on their Sales or Purchase headers, respectively.
In other words, if you create a Customer Card and intentionally leave the address blank, then create a Sales Order and fill in the address information on the Sales Header, without prompting, NAV will update the Customer Card with the address from the Sales Header. If the order creator does not have permission to modify the Customer Card, they will receive a permissions error.
Here's the code from the Purchase Header Table (38), the OnModify trigger:
IF Vendor.GET("Buy-from Vendor No.") THEN
IF NOT Vendor.HasAddress THEN
IF "Pay-to Vendor No." <> "Buy-from Vendor No." THEN
IF Vendor.GET("Pay-to Vendor No.") THEN
IF NOT Vendor.HasAddress THEN
Therefore, if the Vendor does not have an address, it tries to update it with what was put in the Purchase Invoice, even if nothing is there. It is important to note that this feature was removed in Dynamics NAV 2018.
Statical Prism is an easy-to-use productivity tool that offers benefits for just about anyone using Dynamics NAV. Dynamics NAV consultants, developers, QA consultants, supporters, and architects, download Statical Prism today.
In Saurav Dhyani’s recent blog, he compares the changes in the Dynamics NAV service tier between NAV 2017 and NAV 2018 and details the changes on each tab within the service tier: General, dDtabase, ODATA, Azure Active Directory, Task Scheduler. He also gives a rundown of what’s in the new Development tab.
Kyle notes that Microsoft released their support matrix for SQL Server 2017 versus versions of NAV. Kyle explains, “I upgrade my local server from 2016 to 2017 without any issues at all, running against five different builds of NAV. The summary is that 2015 through 2018 are supported.”
This applies only to these two versions of Dynamics NAV. You may need to apply this hotfix due to the security protocol for CRM Online services being updated to TLS 1.2.
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.
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.