Sign in
Microsoft.com
 
Resources for IT Professionals
 
 
 
Resources for IT Professionals > Dynamics Forums > CRM > Owner of child objects changes when parent object is updated - how can this be avoided?
Ask a questionAsk a question
Search Forums:
 

AnswerOwner of child objects changes when parent object is updated - how can this be avoided?

  • Thursday, November 05, 2009 12:36 PMLarsChristian Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi guys.

     

    We're an SMB using several modules of MS Dynamics CRM 4.0, including the Service module and the Sales module. We're experiencing great difficulties with the following scenario:

     

    An Account Manager updates the Account Name, Street Adress etc of an Account object, causing the Owner of all the child objects of this account (Cases, Leads, Opportunities etc) to change to the person who performed the update. As you might realize, this is causing a lot of frustration when suddenly the Account Manager is also the Owner of all technical support cases for the same account, when a technician should in fact be the owner of e.g. the Cases.

     

    Any ideas or input as to how this issue can be avoided or fixed?

     

    Thanks!

     

Answers

  • Thursday, November 05, 2009 12:45 PMMSCRM Blogger Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    This is controlled through the relationships.

    You should be able to change the Assign Relationship

    1. Go to Settings
    2. Customization
    3. Customize Entities
    4. Double click the entity
    5. Click on the desired relationship section
    6. Edit the relationship
    7. Modify the Assign Relationship Behavior
     
  • Friday, November 06, 2009 8:23 PMLeon TribeMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Changing field values on an account shouldn't affect the child records. The only thing that would potentially affect ownership is if the ownership of the account itself changes.

    Perhaps you have a plugin or workflow which is misbehaving.

    Leon Tribe

    Want to hear me talk about all things CRM? Check out my blog

    http://leontribe.blogspot.com/

    or hear me tweet @leontribe
    Want to hear me talk about all things CRM? Check out my blog http://leontribe.blogspot.com/ or hear me tweet @leontribe
     
  • Sunday, November 08, 2009 11:50 PMScott Sewell, CustomerEffectiveMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Agreeing with Leon and blogger - Check the workflow - if the workflow updates the owner of the account, that ownership could cascade down to other objects. -

    Also if you happen to be using SCRIBE, check to make sure no scribe job includes the owner attribute in the DTS, or only updates the owner if the owner is actually changing. - If scribe touches the owner field it effectively kicks off a re-assignment even if it's re-assigning the object from "Scott" to "Scott" (same person.)
    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
     

All Replies

  • Thursday, November 05, 2009 12:45 PMMSCRM Blogger Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    This is controlled through the relationships.

    You should be able to change the Assign Relationship

    1. Go to Settings
    2. Customization
    3. Customize Entities
    4. Double click the entity
    5. Click on the desired relationship section
    6. Edit the relationship
    7. Modify the Assign Relationship Behavior
     
  • Friday, November 06, 2009 8:23 PMLeon TribeMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Changing field values on an account shouldn't affect the child records. The only thing that would potentially affect ownership is if the ownership of the account itself changes.

    Perhaps you have a plugin or workflow which is misbehaving.

    Leon Tribe

    Want to hear me talk about all things CRM? Check out my blog

    http://leontribe.blogspot.com/

    or hear me tweet @leontribe
    Want to hear me talk about all things CRM? Check out my blog http://leontribe.blogspot.com/ or hear me tweet @leontribe
     
  • Sunday, November 08, 2009 11:50 PMScott Sewell, CustomerEffectiveMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Agreeing with Leon and blogger - Check the workflow - if the workflow updates the owner of the account, that ownership could cascade down to other objects. -

    Also if you happen to be using SCRIBE, check to make sure no scribe job includes the owner attribute in the DTS, or only updates the owner if the owner is actually changing. - If scribe touches the owner field it effectively kicks off a re-assignment even if it's re-assigning the object from "Scott" to "Scott" (same person.)
    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell