Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 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 | Upcoming TechTalks
we want to use as much as possible the standard fields in our systems, that why we adjust existing system option sets. We removed all the values, but two from the system option set "Account Type".
On the dev instance, everything looks fine, we only got two values left. However, the changes are not taken over to the test, respectively prod instance. We imported the changes with a stage for upgrade and work with a managed solution. We already tried it a couple of times.
Is it not possible to adjust a system option set? Do we have to create a custom option set?
Thanks in advance!
Did you published all customizations after importing solutions?
yes, of course. Every time we imported a solution.
what is the optionset you want to modify?
Have you checked the solution layers for the attribute?
What do you have there?
I reproduced this problem in my environment.
It seems to be by design.
Please refer to
sorry, but these posts are not really helpful. One is referring to a case with unmanaged solutions and the other one with several managed solutions where the option set is included.
We have this option set in only one managed solution and the layer shows this solution is on the top and active.
Can you give me something official that Microsoft doesn't allow anymore to adjust system option set? I know it was working in earlier solutions.
If you want you can create a service request and post the ticket number here. I will take the ownership and investigate.
thanks for the offer with the service request. We thought it might be a good idea to adjust this field, respectively option set on all instances through the default solution. Do you maybe have a better idea or do you see any big risks doing that?
We know that future solution imports won't have any affect on the field, even if the field is included, but we already lost too much time in investigating how to solve this issue.
Thanks for your advice.
Hi Thomas, I don't think that using the default solution is a good approach in any scenario.
Maybe the optionset has an active layer that prevents a solution import to make changes
as mentioned earlier, there is only one managed solution and this solution is on the top for this attribute.
Business Applications communities