3
votes

I am confused with this feature in CRM13, please help.

In CRM11,

I added some options in the "StatusReason" field for "Inactive".

When i try to deactivate that record from the grid, it will ask you to select the status for deactivation.

When i try to deactivate the record from the form itself, then also same thing happened.

Now my CRM upgraded to CRM13.

In CRM13 ,

deactivation of record from grid will allow you to select the status that is added for the "Inactive" but,

deactivation of record from the form itself, will not allow you to select the status that is added for the "Inactive" rather than this, it will deactivate the record automatically.

Is there any big change happened in this CRM13 for this feature?

Any kind of idea will be appreciated. Thanks in advance.

Thanks, Anish

2
I had one CRM11 online account and i tested it out and i found that deactivation of record from form itself, it will still allow you to select the status. But Same thing does not happens in CRM13 now. Any idea??Anish
Are you trying to deactivate a custom entity or an opportunity/contact/lead/account?user2295317
This is custom entity.Anish
I reported this bug on Connect during the beta for CRM 2013. It was fixed in the Online 2 release. Not sure about on-premises rollups, but suspect SP1 will cover it. support.microsoft.com/kb/2925872AdamV

2 Answers

1
votes

I had the similar experience when deactivating the record from form level. There is no MSDN CRM article related to this. CRM 2013 brand new menu is designed to ease user navigation, free up screen space, remove pop-up windows, etc. Probably part of this strategy this feature has been depreciated. There is nothing being mentioned in CRM Rollup 13. http://support.microsoft.com/default.aspx?kbid=2891271.

The workaround is to hide the deactivate button and make a custom button to invoke a dialogue to set the relevant status reasons.

-1
votes

This was a bug in my CRM Online instance.

Now automatically this has been fixed. I do not know how this is fixed..but I guess after some updates..this got fixed.