Microsoft Dynamics NAV 2013: How to Approach an International Deployment

Companies planning multinational deployments of Microsoft Dynamics NAV need to be aware of some of the common challenges and issues surrounding such implementations.

Before you decide to deploy Dynamics NAV 2013 internationally be sure to consider licensing requirements - something your partner can definitely help you with, according to a presenter from an international food manufacturer at a recent online meeting of NAVUG.

If you have different companies within the same database, be prepared to do customizations, he explained, because NAV isn't built to have one database to support multiple countries.

"Microsoft is moving from some of the localizations with NAV 2013 and going more to a partner-based localization instead of a Microsoft-based localization," said the co-host, an international supervisor for an electronics manufacturer. "So if you're choosing to upgrade to 2013 internationally, you want to do your investigation first on what localizations are available out of the box and what localizations you're going to have to work with your partner on. I would highly recommend that you do the research on what you need on your localization because right now there's [discomfort] across a lot of users who feel that they're not going to get everything they need. So just be aware of what you need."

There are also certain things firms have to do if they plan to start a new international company.  The first thing to determine is the currency of that country, the hosts recommended.

"I recommend that when you set it up, you set it up with the correct legal code for that country, which will make it easier later if you have to do any reporting of it," said one host.

You also need ...