Forum Discussion
Cannot sync Country when connecting greenfields D365 BC <-> Dataverse (and onto D365 Sales)
Hey, sorry for the very newbie question, but everyone has to start somewhere!
I get this cryptic incantation when trying to connect an essentially greenfields D365 BC (a small bit of progress through assisted setup) and a similarly vanilla D365 Sales instance, using the very latest updates on 2025 wave 2 (like I've applied this weeks coming update and any and all of the background app updates etc afaik is totally up-to-date at 28 Sep 2025 - maybe this is new and because we're living bleeding edge, may possibly be a heads up for someone out there, I really dont know.
Cannot sync Country when connecting greenfields D365 BC <-> Dataverse (and onto D365 Sales) - Business Process Error: Choice member name to[o] long. dyn365bc_countryregionaddressformat_v2_0.City_x002B_County_x002B_Post_x0020_Code_x0020__x0028_no_x0020_commax0029
When performing the Dataverse connection and trying to enable all of the available fields, the above error message appears, and no matter what the dropdown is set to, the choice in the error doesn't seem to change, in PowerApps, in Choices, is no entries for 'dyn365bc_country' (but plenty of others), has been setting up for a day and a half half sync'ed, country not published nor trying, but seemingly leaving some of the rest in limbo.
I asked CoPilot, ChatGPT et al and poked around without coming up with anything, didnt pass the google test, thought maybe an MS Call, but we try not to take the mickey and at least try first
4 Replies
- JillArmourMicrosoft
Community Manager
I have sent your inquiry to a team member but they are OOF currently. I will respond here when I hear back. You may want to try posting this in the Find Answers | Microsoft Dynamics 365 Community instead. You may get a quicker response? Have you submitted a support ticket yet?
- JillArmourMicrosoft
Community Manager
This is the teams response (I was pretty close with mine!)
This appears to be a technical inquiry. I recommend starting with a support ticket and simultaneously posting in the D365 Community. This approach may boost the chances of a fast response while allowing the support team to document the error for future reference.
- JoshuaFinleyCopper Contributor
Thank you so so much! Is super appreciated, and will definitely try and follow up posting there when not stuck with a customer - we weren’t sure we were entitled to support / when you’re a tiny partner getting set-up and wanting to use all your MS benefits to have a showcase, we weren’t entirely sure where to go, with my laptop called “stacktrace” figured to start by getting all the right people, and will definitely share if we get an answer in case it helps someone as I can - appreciate the help & forum pointers immensely, once we make sure it’s not just “Josh is new and learning” will definitely log something - after 30 years of looking after infrastructure, know that enterprise app managers don’t always want to press that upgrade button straight away, so definitely figured that just in case it’s like SharePoint v1 where somehow I get to find a first in world genuine bug to start taking good notes, while simultaneously hoping is just me!
- JillArmourMicrosoft
Community Manager
😆"josh is new and learning" cracked me up. Thanks for your response! Glad we could help a bit. Looking forward to seeing your answer when you get one! Good luck