Dynamics 365 F&O (Finance and Operations) requires a different approach to customizations than what we were usually accustomed to in AX. One of the most significant changes is that we can no longer overlay our code; we now need to create extensions that will work with Microsoft’s upgrade cadence.
Lucky for us, there exists a handy feature in D365 F&O to improve the customizations for specific countries and maintain the functionalities working only for the needed countries.
Today I would like to talk about the CountryRegionCodes property. This property allows us to keep the functionalities separated by geographic region. It allows displaying or hiding functionality/objects depending on the selected legal entity and the Country it is configured in.
You may find the CountryRegionCodes property in the following Application Object Tree (AOT) elements:
In the following standard table in AX 2012, we have the property for the table Accountant_BR set to “BR” (Brazil). In this case, this table only appears in the Menu for the Legal entity that has the Primary Address with Brazil Country.
In D365 F&O, we have the same property for the list of the same objects before, and it’s a set of powerful features we need to use, for example, Develop Customizations like Localizations for specific Countries (LATAM Localizations in my case).
The list of Country Codes is based on ISO 3166-1 alpha-2; you can find the complete list here.
In Pangea Consultants, we have our Localization products work with this functionality and others that we will mention in the following posts.
Utilizing this approach in conjunction with other best practices, we can maintain more than one Localization within the same environment without having to maintain multiple code sets that simplify implementation and speed up end-user adoption.
