how to create multiple companies with different localization

(0) Share

Report

Posted on by Community Member

Hi,

Can anyone please advise a step by step guide on how to create a company with different localization.

Currently I have one company with Russian localization, and I need to create a new company with W1 localization that should be on the same database and same server instance.

Thanx in advance

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Community Member on at

Like (0)

Report

I don't think so, this can be achieved in standard NAV due to System Design. Microsoft provides different Databases for different localisations (Countries)

Although it is available with many of the ERPs, NAV does ot support such as standard functionality.

You may need to go for Customisations to achieve this.

Or better You create separate DB for the same.

Was this reply helpful? Yes No
Suggested answer

Suresh Kulla 50,243 Super User 2025 Season 2 on at

Like (0)

Report

In NAV each localization is different you cannot have different companies in one localization database, the database you use is specific for a localization so you need to create different localization databases instead of different companies. You can create different companies by using one localization database i.e. use W1 to create US and DE companies but it will not have any localization specific changes.

Was this reply helpful? Yes No
Suggested answer

Alexander Ermakov 28,096 on at

Like (0)

Report

Actually, it IS possible :-).

NAV does not have layers as AX, so one database has its own set of modified and added objects. Thus, if you have a localized database with one company, you can theoretically merge it with a different localization, but it is actually quite a challenging task. The changes of one localization will be visible and active for all the other users, so it is a huge task just even to hide those fields that are needed for one users and not needed for the others.

However, if you already have a Russian localized database, you should know, that it is one of the most complex localizations in the world, competing with Brazil and India. It basically includes all the functionality of W1 version, but has on top of that quite many local features.

You can eliminate most of the localization features on a company level by turning off "Russian Accounting" flag in the General Ledger setup:

Of course, you would need to make more settings, related to specific accounting features, but this is a major one.

This version should basically not differ much from a W1 version. For more information, I recommend to contact trusted local partner in Russia.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks all for explanations.

What about having 2 companies each on its own database but both on the same server instance.

I just need a simple workaround to NAV limitations. Trying to deploy multitenancy but don't know whether that will help me.

Or let me ask the question in other words. The CEO of both companies have user account, and he wants to have access to both companies and the data in there without switching the NAV server.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Better you deploy two different databases for different localisations.

You can create two separate instances and create two Nav application icons at desktop so that you can easily access the respective instances.

Multitenancy may not needed at this point in time.

Was this reply helpful? Yes No
Suggested answer

Alexander Ermakov 28,096 on at

Like (0)

Report

As I have mentioned, you can still have two companies - one using Russian localization and another - not using Russian localization, in the same Russian localized database, therefore your CEO could switch just between the companies. Russian localization in most cases does not substitute W1 functionality, but rather add new features on top of that.

For the company that should use W1 functionality, you just need to do a certain (different) setup in order not to use the most of the localization features. E.g., you would need to setup VAT posting groups in a different way for each company.

We have had samples of such installations, and it worked fine, and it does not require development or customization. You do not need multitenancy for that.

Was this reply helpful? Yes No