locked
Opportunities assignation RRS feed

  • Question

  • Hi everyone,

    This is the situation. When i create a new opportinity or update one and change the owner, Dynamics CRM 4.0 auto-assing all the opportunities of the account to the new owner. Can you help me please?

    thanks a lot

    angel

    Tuesday, June 14, 2011 11:13 PM

Answers

  • This is managed by the cascade behavior of the relationships. You can navigate to your entity (opportunity) see the relationship it has with account and verify what cascading behavior it has.

    You can read more on cascading behaviors here:

    http://msdn.microsoft.com/en-us/library/gg309412.aspx


    Gonzalo | gonzaloruizcrm.blogspot.com

    • Marked as answer by Jim Glass Jr Wednesday, June 15, 2011 7:29 PM
    Wednesday, June 15, 2011 6:02 PM
    Moderator
  • As mentioned, this has to do with cascading behaviour, so when you change the owner of an account it will update ownership on some other records below it (not opportunities out of the box, by the way), or when you change an opportunity owner it could also assign the activities below that. On custom entities or relationships you can control whether CRM updates all records, only open ones or none However, you have something odd going on, because you say you update an opportunity and that updates the other opps belonging to the same account, which is not something done out of the box. You could cause that to happen if you had a workflow (or plugin) which updated the parent account to re-assign it, and cascading behaviour updated the other records, and if that is the case you should be able to identify it quite easily. It's definitely odd!
    Wednesday, June 15, 2011 8:13 PM

All replies

  • Hi Angel.

    Plugin or custom workflow will be suitable for this situation. In that you ned to fetch all the opportunities of that account and change the owner to current user.

    This plugin or custom workflow should be set to trigger on Create and Update events of the opportunity.

    For fetching records by account use 'QueryByAttribute'.

    For assigning records to current user use 'AssignRequest'.

    Thanks and Regards

    Ramu

    http://www.osmosys.asia

    http://osmosee.wordpress.com

     

    • Proposed as answer by Janu_m Wednesday, June 15, 2011 3:16 AM
    Wednesday, June 15, 2011 3:16 AM
  • Thanks for your answer Ramu..

    But the situation i posted, is it the way that CRM works out of the box? i think CRM should not do the auto-assign, unless a workflow or plugin exists (this is not our case) right?

    I think i didn't explain that my post is an actual problem insted of something that i wanted to do..

    angel

     

    Wednesday, June 15, 2011 5:15 PM
  • This is managed by the cascade behavior of the relationships. You can navigate to your entity (opportunity) see the relationship it has with account and verify what cascading behavior it has.

    You can read more on cascading behaviors here:

    http://msdn.microsoft.com/en-us/library/gg309412.aspx


    Gonzalo | gonzaloruizcrm.blogspot.com

    • Marked as answer by Jim Glass Jr Wednesday, June 15, 2011 7:29 PM
    Wednesday, June 15, 2011 6:02 PM
    Moderator
  • Thanks Gonzalo, but the problem is when i change the owner of one opportunity.. When i do that, all the opportunities of the same account change with the new owner of the opportunity updated. Still, i will check the information you send me.

    angel                 

    Wednesday, June 15, 2011 7:59 PM
  • As mentioned, this has to do with cascading behaviour, so when you change the owner of an account it will update ownership on some other records below it (not opportunities out of the box, by the way), or when you change an opportunity owner it could also assign the activities below that. On custom entities or relationships you can control whether CRM updates all records, only open ones or none However, you have something odd going on, because you say you update an opportunity and that updates the other opps belonging to the same account, which is not something done out of the box. You could cause that to happen if you had a workflow (or plugin) which updated the parent account to re-assign it, and cascading behaviour updated the other records, and if that is the case you should be able to identify it quite easily. It's definitely odd!
    Wednesday, June 15, 2011 8:13 PM
  • If you assign the opportunity to a new owner, what happens to the account owner? Is it also updated or it keeps the old value?

    Gonzalo | gonzaloruizcrm.blogspot.com

    Wednesday, June 15, 2011 8:31 PM
    Moderator
  • The owner account is also updated.. i saw the problem in the workflow.

    Thanks a lot Gonzalo and Adam,

     

    regards,

    Angel

    Wednesday, June 15, 2011 9:28 PM