The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Personalized Community is here!
Quickly find the content you seek
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
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
I recently had a few issues with Status Reasons and the number associated with a status reason
CRM 2013 – Understanding Status and Status Reason – think before deleting them
This lead me to have to add a Status Reason into CRM using CRM SDK because I couldn’t figure out where the default number of a new status reason was being calculated.
CRM 2013 – How add a status reason using the CRM SDK
Today I figured out where the number was coming from when you create a new option set. This value is set in the publisher. There is a field called Option Value Prefix
When I go into my Hosk Solution, which uses the Hosk Publisher and create a new option set, it takes the default value from the publisher
The default value is also used for new Status Reasons
The default solution includes all the customizations in CRM and this is the solution you access when you choose customize the system.
To understand solutions read more in the blog post below
CRM 2013 – Understanding Solutions and how they work
What values will be used when you add a new option set or status reason when editing the default solution
The status reason seemed to still use the default value in my new publisher. This was unusual because I would have expected it to use the value in the Default publisher which was 10000 because this is the publisher specified in the Default Solution? The default publisher is read only so this cannot be changed.
I did a bit more digging and found CRM seems to calculate which solution the entity is in and then uses the solution option value prefix even if you edit it using whilst in the default solution.
When I added a new optionset it did use the value in the default publisher
Business Applications communities