Dynamics 365 for Operations – Localized functionality region

I have been searching for different ways to configure and store configuration and use it when I create new a legal entities in the same environment or in another instance:

• Manually configuration
• Export configuration data packages from configured legal entity and import it in the legal entity being configured
• Export configuration, store the data packages in Asset library LCS and Import data packages from Configuration & Data manager in LCS to the relevant environment / legal entity
• Full copy of the environment to another instance in the project
• ISV solution that can push / pull configuration from a Master legal entity to the legal entity being configured

Best approach depends on the situation. :-)

Microsoft are aware of the present functionality can be approved, and according to the roadmap the Spring 2017 release contain two improvements within that area:

“Copy configuration:

Users will be able to easily export their configuration data and move it from one instance to another instance. This will save time by allowing implementers to take a golden template and export it in a single step for use in another instance. The feature will have the necessary entities and sequencing needed to be able to complete this process in a single step.”

“Copy one legal entity to another:

As new companies are needed, users will be able to save time and potential errors by copying an existing legal entity’s setup to the new company. This will allow the onboarding of a new location to be quick and consistent with the company’s golden template design.”

During my search for the best approach I came across the “Localized functionality region” functionality:

Create new legal entity

You meet the functionality when you create a new legal entity, after you have typed the basic information: Name, Company and Country/region and pressed OK.

When the legal entity is created D365 automatic select “Detect using company address” in the ”Localized functionality region” field:

It is possible in this field to select between 35 different countries and “None”. You can change the selection in the field until you make the first transaction in the legal entity. If you select another value than “Detect using company address”, either you get the country/region functionality from the country you select in the field or you get no country region functionality if you select “None”.

Denmark as localized functionality region in a USA address company

I select Denmark as localized functionality region for my USA address company.

I have been through several modules and menu items to find the impact, and as expected, there are differences in the Tax module. If I did not select Denmark but use the default value “Detect using company address”, no foreign trade functionality are included in the USA company.

When Denmark (EU country) is selected, foreign trade functionality is available in the USA Company.

None as localized functionality region in a IRL address company

I select “None” as localized functionality region for an Irish address company.

“None” seems to remove all country/region functionality in the legal entity, e.g. foreign trade functionality.

Conclusion

The Localized functionality region are available, and can be used for some purposes.

One purpose can be to avoid configuration in a legal entity where you only need the basic functionality but you have to spend more time configuring the legal entity if you do not exclude local functionality. Selecting “None” or another country might provide the functionality you need.

Another purpose can be a workaround if you use a different accounting currency than is used in the company country. Some functionality are require you use this currency, e.g. Settle and post tax require accounting currency EUR if the country/region code on your legal entity is NLD. Selecting another country might provide the functionality you need and you come around the currency issue.