locked
Cascade activate/deactivate - is this possible in CRM 4.0? RRS feed

  • Question

  • Hello,

    We have relationships like:

    Account -> Site (1:many)
    Site -> Record (1:many)

    I would like the ability to allow a user to deactivate an account, and have the deactivation cascade to all that account's sites and all the sites' records.  I have played with different flavors of 1:many relationships, but I'm not seeing this happen, and don't see the ability within the parental, or configurable cascading options.

    Any ideas?

    Cheers,
    gg
    Friday, October 30, 2009 7:46 PM

Answers

  • If you want a no code solution, you should be able to create a workflow for Sites and Records OnCreate and have the workflow wait until their parent record's state is deactivated and then deactivate themselves. The disadvantage is potentially a lot of workflows kicking around waiting.

    Leon Tribe

    Want to hear me talk about all things CRM? Check out my blog http://leontribe.blogspot.com/ or hear me tweet @leontribe
    • Marked as answer by Jim Glass Jr Tuesday, November 3, 2009 4:27 PM
    Tuesday, November 3, 2009 12:26 AM

All replies

  • Hi.

    This can be done using plugin which will handle SetState and SetStateDynamicEntity messages.
    Truth is opened the prepared mind My blog - http://a33ik.blogspot.com
    Friday, October 30, 2009 8:19 PM
    Moderator
  • Hi,

    You can't do this out of the box with relationships.  You either need to use plugins or another method using teh web services.
    Alex Fagundes - www.PowerObjects.com
    Friday, October 30, 2009 9:03 PM
  • Thanks Andriy - I will give this a shot.  If you know of any sample code, please post it.  I have only written a couple of simple plugins and still have a lot to learn.

    Thanks!
    gg

    Friday, October 30, 2009 10:27 PM
  • Hi geeky,

    you can do it using custom workflow also.
    Saturday, October 31, 2009 12:05 PM
  • If you want a no code solution, you should be able to create a workflow for Sites and Records OnCreate and have the workflow wait until their parent record's state is deactivated and then deactivate themselves. The disadvantage is potentially a lot of workflows kicking around waiting.

    Leon Tribe

    Want to hear me talk about all things CRM? Check out my blog http://leontribe.blogspot.com/ or hear me tweet @leontribe
    • Marked as answer by Jim Glass Jr Tuesday, November 3, 2009 4:27 PM
    Tuesday, November 3, 2009 12:26 AM
  • Hi,

    I have about same scenario. Based on Account entity, there are lots of other child entities present whch have parent child relationship.

    In case an account is deactivated, all the chilrd entity records should be deactivated. Same in case of activation.

    Also the ativation/deactivation of the Account entity record will be done through an .Net application.

    Can I trigger workflow or pug in based on the above scenario??

    regards

    joon

    Tuesday, March 30, 2010 11:11 AM