Skip to main content
Submitted by Suzanne Scanlan on 22 September 2017

ArcherPoint Dynamics NAV Developer Digest - vol 158Developer Dude

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 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.

How Many Country Versions of Dynamics NAV Can Be in One Database?

Jamie is looking for a list of what countries can be in the same Dynamics NAV database. For instance US, Canada, etc. She found that Mexico cannot be in a US dB and wanted to know what other issues she may come across.

Matt T: I think, as always, the answer is it depends. I've run Netherlands and UK in a US database with none of the localizations for those countries.

Kyle: Cronus has US, Canada, and Mexico all in the same database. 

Saurav: As Matt Traxinger said it depends on localization. If you plan not to use any localization, then you can use W1 release and create all countries within the same database. But Microsoft releases NAV localized versions based on similar localization, grouped together. In NAV-XXX-US you will find companies of US, Canada, and Mexico. Each company is setup for different taxation or regulatory feature specific to that country.

It can be changed in future based on country-localized rules. In earlier releases, up to 2009, there used to APAC (for Asia Pacific) but now that has been changed and AU & NZ and comes on the same DVD where as other Asian Pacific countries have a separate one. Microsoft has grouped countries for releases; NAV 2017 is not yet released for India.

You can always get a fair idea from the download page of Product DVD or Cumulative Update. Refer to this site for NAV 2017. As of now, NAV 2017 is released for W1 & 19 localized versions, specified on that page. Reference the “Detail” section.

An Argument for Test Driven Development (TDD)

This blog from Medium, The Outrageous Cost of Skipping TDD & Code Reviews, shares some interesting stats:

  • Average time to fix bug during development (using TDD, which includes writing the test of course): 1 hour
  • Average time to fix a bug in test DB by users/testers in test or production: 15 hours

That's a whopping 15 to 1!

Share your thought in the comment section below...

Microsoft Dynamics NAV Development Preview – September Update

Highlights in this month’s development preview:

  • The .navx file extension for AL packages has been changed to .app
  • The developer endpoint on the Dynamics NAV server now performs license checks when publishing AL projects
  • The developer endpoint on the Dynamics NAV server now performs permission checks to see if the user who is trying to publish an AL project has the rights to do so
  • It is now possible to define Watches and conditional breakpoints in the new debugger

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.

Blog tags