Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
We're in the process of moving across to D365FO and are going from largely free-text address recording to the proper structure of D365FO. We figures that the out-of-the-box setup was probably going to be pretty good, but actually, we're finding that it's way off of the mark!
When looking at the Wikipedia page on address structures around the world and also with local postal companies for specific countries, we're finding that the D365FO defaults are some way off. E.g. the D365FO setup for New Zealand includes the state, but the New Zealand post office indicates that state should not be included in the address.
Here are the countries that we're changing the default for so far:
What's your experience?
You can set up the address formatting in the Organization Administration module, go to Organization Administration --> Global Address Book --> Addresses --> Address Setup.
Here you can define address formats (or choose one of the pre defined ones) and you assign these address formats to the country/region.
This way you can customize the formats per country.
Hope this helps.
Thanks for the tip, but the post isn't so much a question of "how" as "why" (possibly a poor choice of words for the title). Why are so many of the default address formats 'wrong'? Surely a company with such a broad client base from all of these countries would do a better job of setting up the defaults?
I would agree on that part, but I think it is a matter of priority setting on the side of Microsoft. Since there is a work around to configure your own formats there is not much priority I guess to update the addresses.
A thing I can not understand is that the street setup always includes the housenumber, I would like to see the street, house number and house number extension to be accounted for in seperate fields. This would make creating certain reports a lot easier.
Agree, this must be a matter of priorities and budget allocation within Microsoft. In other words: nobody cares. All those standard address formats are utterly wrong.
@ Ties: if you split the house number, you have nowhere to place the office number or any other info that follows the house.
From experience, it is wise to define one default format Street - Zip - City - Country for most of the countries, and add the mandatory State for at least:
I.e. you can go pretty far with just 5 address formats. Beware of Russia, they hard-coded a crazy logic as soon as you select "RUS" as a country. I spent weeks trying to prove to the MS Support how wrong they are - all in vain (talking about their priorities).
(I work with Stuart)
So far we have found incorrect default address formats. If costed our time or our D365 partner's time at say £500 and this is something that we had to investigate and now will have to fix in multiple environments then the cost to us is at least £1000.
We made development decisions on the assumption that MS would've set the defaults correctly. Obviously I'm going to ask for a refund! :-)
Good luck with that. Sometimes, very rarely, Microsoft do refund the customers, but they do that only if the directly implement through the Microsoft services division.
Hi Jon, Stuart,
What would it cost you if you had to setup all data from scratch? Note that your claim will probably not be granted as Microsoft is not responsible for the data in your environment. They might be responsible for a correct working system. Microsoft did provide some examples many years ago. I do agree they are not perfect. Probably the person responsible at Microsoft is not even aware. Did you create a ticket for Microsoft or submitted an idea on the Dynamics experience website? Note that also partners can provide a data pack as addition on the default setup.
We expected global default data setup to be good. It's reasonable expectation otherwise it'd be ok for MS to create new environments with nil data.
We made a support request via Services Hub. I've asked the if the fix is just for us or for all recipients of the Demo database i.e. the default data setup.
I have been informed that any fix re our service request is only for us. So folks - get voting if you want this fixed for everyone. (How/where is the voting done?)
You can go to the Dynamics experience website and search for an existing idea and vote for it or create a new one. (experience.dynamics.com/)
Here is an idea that I raised. If you want it, give it some love:
Business Applications communities