web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Unanswered

Configuration of ISO 3166-1 Alpha 3 Codes

(1) ShareShare
ReportReport
Posted on by 5
  We recently switched over to Dynamics 365 Sales after being a long-time customer of Salesforce.  Overall, I'm finding the data model much more intuitive and flexible than what I was used to in the Salesforce CRM world with one major exception which is getting the system to properly recognize our standardized ISO 3166-1 Alpha 3 Country Codes (https://en.wikipedia.org/wiki/ISO_3166-1_alpha-3) and Alpha 2 State Codes.
 
  What I would like to do is allow only ISO codes in the data storage (for consistency) but allow the users to select the full country codes in the UI.  Is there any standard functionality for doing this because after a lot of searching I have not yet found anything.  Salesforce had some functionality called Dependent State and Country Picklists (shown in a video here: https://youtu.be/lzvo1d1r2Rs?si=TijnnI6r94iQTx8U&t=521) that made for an intuitive user interface.  A consultant that we worked with for our implementation created two custom tables with these Country/State lookups for us.  This is what the user-interface looks like: https://app.screencast.com/X83pbDVK6JjcU   But we're finding multiple downsides to this solution such as...
 
  1. Behind the scenes, all the standard address tables (leadaddress, customeraddress) are still using the country/stateorprovince columns for things like maps, sales territories, etc.
  2. We would have to setup foreign keys in each table that uses addresses and, in most cases, multiple foreign keys per table.
  3. I believe to address #1 we're going to have to setup multiple Power Automate flows to update the default fields each time these fields are updated.
  Do you know of any links to resources that walk through configuring this?  For consistency in data entry and reporting, I don't think we want users typing in whatever they want into these fields as that will be an inconsistent mess.  FWIW, all of our standard form entry methods are already using these ISO codes. In general, if and where standard functionality exists, I prefer to adopt it rather than trying to work around it and I'm finding it hard to believe that Microsoft doesn't have best-practices for addresses in this regard.
 
  Any help you can provide would be greatly appreciated.
Categories:
I have the same question (0)

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
ManoVerse Profile Picture

ManoVerse 176 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 139

#3
CU11031447-0 Profile Picture

CU11031447-0 100

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans