Brutus Online

Another short one for CRM 4.0…

Today someone from Sales department tried to assign an entity (this time a Contact, previous time an Account) to someone else. In cleaning up and/or deviding contacts within the Sales team, this is a daily routine and common practice for our Sales people.

The error that the Sales person got had something to do with insufficient permissions on assigning an entity and that the role he/she was in, did not have enough permissions :

My first thought was : bullshit!

In my search for an answer, I discovered some interesting facts… (and a sleezy solution of course! )

• The standaard role that the Sales person had, was enough to assign entity-records to himself or anyone else.
• Even the CRM System Admin user could not assign the entity-record to someone.
• Other entity-records are easily assigned to other people.

Solution

This is just a temporary one (hopefully), until we install Update Roll Up #4 :

1. Give the System Administrator securityrole to the CRM-user that got the “insufficient permissions” error.
2. Let the user assign the entity-record to the designated CRM-user.
3. Remove the System Administrator securityrole.

That’s that! If there is anyone in CRM world that had this same problem, please leave a comment! I’m interested in a more… well… a better solution

This entry was posted on Tuesday, June 30th, 2009 at 22:40 and is filed under CRM. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.