Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
I was applying updates to production by Importing Solution with Customizations. Turned out that StringMap attributes got updates as well. StringMap attributes were update on production opnly and not in dev version.
My question is how to avoid in the future and how do I fix it now? I have a production database copy prior applying changes.
Stringmap holds the optionset values and labels of an environment. If you have applied some changes to optionset by importing solution in Production, it is going to update Stringmap. If the customizations are applied by exporting it from dev, then the same customizations should also exist in Dev environment too. If you can share more details, we will be able to share possible solutions.
If found useful, pleas mark this answer as verified.
Business Applications communities