« Leveraging Microsoft CRM 2013 and Core Motives for Events and Surveys | Main | Customer Effective's Dynamics CRM Winter Webinar Series »

January 13, 2014


Scott Sewell

Nice work, Joel - Bookmarking this post for sure.

Scott Sewell

Great stuff Joel! - This delivers the good stuff.

Priyesh Wagh

Nice Post,
Actually, I have an issue deploying Access teams to other CRM instance.
Whenever I deployed, the access team subgrid did not let me add users saying that I don't have appropriate permissions (where I had). So, simply deleting the subgrid from the form and adding it back again resolved the issue without manipulating anything else. But that is not favorable.
Where did I go wrong?

Any idea what can be done? Thanks in advance.

Hitachi Solutions CRM

To avoid this happening, move the data from the teamtemplate entity to your other instance, including the GUID (ID). The problem you saw was the subgrid references the GUID of the access team template, and since that template ID does not exist in the new org, it cannot find it. By first moving the team template records, including the ID, you will be able to move customization between orgs.

Mauro Ippolito

Good job Joel, it is very clear now. But I have a simple question:
What are the differences between
- using Access Team
- sharing the record directly to the wanted users (in this case you don't need to manually create a team too) ?
I mean, it seems that the only difference is that with access team , you can see the users tha share the record directly in the grid within the form, without going in the share section; in this way, it is even possible to use th advance search; but, only this?
More over, the sahre function is also available in the views list, and it is possible to share multiple record to the same person, filtered for example by an advance find.
Many thanks in advance.

Hitachi Solutions CRM

sharing with users creates a much greater performance impact. When you share a record with 5 users, 5 records are created in the POA table (and many more downstream with sharing cascading). Sharing with a team or using access teams creates one POA table record for the team, no matter how many people are on the team. Team sharing and access teams are similar from a POA standpoint, access teams have lower overhead as they don't have all of the relationships like queues that owner teams do, they are also more user friendly as it is very easy to see whom the record is shared with. Just sharing with users/teams it is not obvious to users who view the record who the record has been shared with.

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment

Comments are moderated, and will not appear until the author has approved them.

Your Information

(Name is required. Email address will not be displayed with the comment.)

Twitter Updates

    follow me on Twitter