locked
Challenging Scenario RRS feed

  • Question

  • We have a client that has individual agents that do not have defined territories and want ownership of their Accounts/Contacts such that other Agents cannot view, read or write to their owned accounts/contacts.  This means 2 agents could potential call on the same account or contact, for the same or different projects.  How do we enable the agents to only see their owned accounts and contacts, yet enable marketing to have single instances of each Account/Contact?  They do not want to send multiple marketing materials to the same contact because there are dupes in the system.

    Any ideas are appreciated!


    Ken Compter
    Monday, December 13, 2010 6:03 PM

Answers

  • Aha ok. A few options. Periodic running of dupe checking by marketing followed by a merge and share for dupe records. Also read-only access for the agents may be an option so the dupe detector kicks in for them.

    Leon Tribe

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

    http://leontribe.blogspot.com/

    or hear me tweet http://www.twitter.com/leontribe

     


    Want to hear me talk about all things CRM? Check out my blog http://leontribe.blogspot.com/ or hear me tweet @leontribe
    Thursday, December 30, 2010 3:44 PM

All replies

  • you might need something like http://mayankp.wordpress.com/2010/06/08/multiple-owners-on-crm-4-0-entities/

    just be aware that this would be unsupported customization and make sure you try and test all scenario in local VM first then development, UAT environment then apply this to Live environment.


    MayankP
    My Blog
    Follow Me on Twitter
    Monday, December 13, 2010 10:22 PM
    Answerer
  • Thanks for the response.  It looked like a party lookup in the screen shot?  Could not connect to the original blog that describes what they did to get that field.  
    Ken Compter
    Tuesday, December 14, 2010 5:18 PM
  • Tuesday, December 14, 2010 6:56 PM
    Answerer
  • You should be able to set this up with standard security. If we have the marketing users associated to the parent BU and the agents in a child BU then setting up a roles such that marketers get access to BU and child records and another role for agents where they only get owned record access solved the problem.

    Leon Tribe 

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

    http://leontribe.blogspot.com/

    or hear me tweet http://www.twitter.com/leontribe

     


    Want to hear me talk about all things CRM? Check out my blog http://leontribe.blogspot.com/ or hear me tweet @leontribe
    • Proposed as answer by Leon TribeMVP Wednesday, December 29, 2010 10:33 PM
    Wednesday, December 29, 2010 10:32 PM
  • Leon, thanks for the reply.  The problem is that agents in the child BU create duplicate Accounts and Contacts (since they are not sharing).  The marketing BU then has duplicates when they try to do campaigns resulting in multiple touches.

     

     


    Ken Compter
    Thursday, December 30, 2010 2:19 PM
  • Aha ok. A few options. Periodic running of dupe checking by marketing followed by a merge and share for dupe records. Also read-only access for the agents may be an option so the dupe detector kicks in for them.

    Leon Tribe

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

    http://leontribe.blogspot.com/

    or hear me tweet http://www.twitter.com/leontribe

     


    Want to hear me talk about all things CRM? Check out my blog http://leontribe.blogspot.com/ or hear me tweet @leontribe
    Thursday, December 30, 2010 3:44 PM