In this webinar, our experts showcase a variety of demo use cases of how different components of the...
A lot of attention in the CRM 2013 Spring wave releases has been focused (rightly so) on enhancements in the areas of Marketing, Service and Social areas. This blog focuses on a specific enhancement in the area of Status Reason transitions in Dynamics CRM 2013.
There are many business cases wherein if a record (for example, a case) has a certain Status Reason you would want to restrict what other Status Reasons the user may select. In the past this was achieved using customizations, more specifically using JavaScript to code this functionality. As part of the Spring '14 update, this functionality is available as a standard option for the Case entity and also for any custom entity.
How to Set Up Status Reason Transitions
The following steps below will illustrate the steps to set this up using the Case entity which has been renamed to "Incident" in this example.
Below you will see the "Status Reason Transitions" window opens. The Current Status Reasons are available on the left. And for each of the Current Status Reason one can specify the available New Status Reasons. The flag icons correspond to the following:
4. Use the New Status Reasons column to list the status reasons that should be available to the user based on the Current Status Reason. For example below, if the Case has the status of "Pending Denial" then the only the "Denied" Status Reason is available as the next Status Reason selection for the user. Once done the "Enable Status Reason Transitions" check box needs to be enabled.
5. Save the transition and publish the changes to the entity.
6. Now test your transitions by visiting the form for the record below.
As shown this is a useful functionality that can very easily be set-up using the available standard functionality as opposed to needing to use any customization. As stated earlier this functionality is also available for custom entities.
Happy CRM'ing!
Hi Joe
we configured the same like above, but on change is firing multiple time for each status.
For Example:
we have 4 values Active, On Hold, Retired, Rejected
we have a functionality on change event, if you select Active once popup will come to update some required field, it should popup only. but in carina update for CRM it is throwing alerts for 4 times. could you please let me know the reason and the solution for this.
Thanks in advance,
Yamuna
Hi
we configured the same like above in our crm 2015 update(Carina online instance), but on change event is firing multiple time for each status.
For Example:
we have 4 values Active, On Hold, Retired, Rejected
we have a functionality on change event, if you select Active one popup will come to update some required field, it should popup only once. but in carina update for CRM it is throwing alerts for 4 times. could you please let me know the reason and the solution for this.
Thanks in advance,
Yamuna
Hi - To help debug the issue, we'd recomend turning on auditing. Then check in teh audit logs to see if perhaps we are are going thru all 4 status reason. OR the events are firing even though we are NOT going thru the 4. We often use auditing to help debug strange items like this and see which workflor or integration is changing the data.