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
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I have a custom entity and it should have status fields for approval. Upon clicking of button, the status fields should change.
Now, I know that we cannot customize the OOB Status field.
But can I use OOB Status Reason field to add my values like Draft, approved, submitted?
Or should I create a custom status field for this?
Thank you for your query.
Yes, you can customize the Status Reason field as per you needs.
You can also map it to appropriate Status Code, for example:
If you map the status reason to proper status code, the record will be read-only accordingly (and you don't have to handle this).
For example, when the record is submitted, it should be read-only, and cannot to be updated unless it is Rejected. If the submitted is mapped to Inactive Status code, it will turn read-only automatically, and when it is rejected, it will be enabled for editing again.
Now, in some scenarios, it is not wise to use Status Reasons for approval, for example:
For us, Membership Certificate status is either Applied, Issued or Expired. We cannot mix it with approval process, in this case will create a custom optionset field(probably global optionset).
To summarize, there is no harm in using Status Reason for approval process, however think this through and map the whole process and verify if it translates to your business terms.
Thank you so much for a detailed explanation. I will certainly use a custom option set then..
Just a last question. If I use custom status option set, how can it be linked to OOB Status field. For example, OOB Status value "active" should be linked to custom option set values draft, submitted, approved. And OOB status value "inactive" should be linked to custom option set value Disqualified.
You cannot link an optionset with Status Code (other than the status reason).
There is no simple approach here.
What you can do is:
Another approach is to create a seprate form which has locked fields, switch this form based on your optionset value.
Ok, thanks a lot! :)
You are welcome
Business Applications communities