Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Status Reason and Record Deactivation - CRM 2013 Online RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    2
    Sign in to vote
    I'm baffled: I have a custom entity with multiple Status Reasons for Inactive records. Which seems a reasonable way to capture the reason why a record is being deactivated. Or at least it was for CRM 2011. In CRM 2013 there seems to be no way to set a Status Reason different than the default one when deactivating a record.

    Please tell me that I am doing something wrong and that the answer is right before my eyes, because I certainly don't want to use a Dialogue or a Workflow. What am I missing?

    Thanks for your help!

    Infusion | xrm2011.wordpress.com | @fantocci

    Friday, January 10, 2014 6:36 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    You need to customise your entity and add another status reason to the deactivated status. Then when you select the deactivate button you will be prompted to select the status reason from a drop down list.

    Hope this helps,

    Scott

    Scott Durow
    Blog www.develop1.net    Follow Me
    Rockstar365
    If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful"

    Monday, January 13, 2014 11:14 AM
    Answerer
  • Question
    Sign in to vote
    1
    Sign in to vote
    Hey Scott, firstly thank you for your answer, but I want to make sure I understand before I make changes: I already have many status reasons for the deactivated status. With CRM 2011 I did get the drop down list, but after upgrading to CRM 2013 (the current Online version I mean) I get nothing. The record goes straight to deactivated with the default status reason.

    Infusion | xrm2011.wordpress.com | @fantocci

    Monday, January 13, 2014 7:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This appears to be a question asked by several others but with no definitive answer from what I can see. I can confirm the same behaviour here on custom entities (with native entities exhibiting the original behaviour that we saw for all entities in CRM 2011).

    Your design is valid and supported - the fact that it worked in CRM 2011 and is not flagged in the "What's Changed" release notes for 2013 go some way to validate this. In the absence of any word on this in the Microsoft CRM SDK (or indeed any content that I've seen from Microsoft thus far) I might assume that this is either an undocumented change or a bug. Given the "quality" of the last two CRM 2013 releases I suspect it's the latter. 

    I've raised a support ticket with Microsoft to try and understand their official stance and will feed back here!

    Tuesday, January 14, 2014 1:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am experiencing exactly the same issue. Any feedback from Microsoft yet? Please keep me posted!
    Friday, January 24, 2014 2:23 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Microsoft support have confirmed this to be a known issue which is due to be fixed in Update Rollup 2. There is currently no date available for the release of UR2 but this post by the Microsoft Premier Field Engineering team is usually helpful in that regard.

    Friday, January 24, 2014 8:54 AM
  • Question
    Sign in to vote
    1
    Sign in to vote
    The bug will be fixed for Online instances with Online2 upate, scheduled for 3-7 February 2014, more information here: http://support.microsoft.com/kb/2925872/en-us
    No news yet regarding UR2 for OnPremise.

    My blog: www.crmanswers.net - Rockstar 365 Profile

    Tuesday, February 4, 2014 11:03 AM