The difference between Append and Append to in CRM

Most of us gets confused with these 2 privileges.

Why do we have 2 like this. Does these work differently?. 

The answer to this is YES. They do work differently.

Append privilege goes with the entity that you are currently working with. We are trying to append a record. This normally works with a child entity.

Append to Privilege goes with a parent entity. Where a child entity has a look up for the parent entity and if they want to select a record from the parent entity then we should have append to privilege on the parent entity.

Eg: - Lets take Account is the parent entity and contact is the child entity. If we have to add a contact to account entity(Account is the primary and Contact is the Child entity), we should have Append on Contact and Append to on Account entities.

There is a very good article written about this. Please check this out also.

http://blogs.msdn.com/b/crm/archive/2009/11/18/microsoft-dynamics-crm-append-vs-append-to-what-s-the-difference.aspx

CRM 2011 - Creating a new Security Role

As we all know we can create a new security role that we won't to assign to a user from scratch in any version of CRM(2011, 4, 3,1.2).

When you do that the user is normally able to log to the CRM system. However with CRM 2011 there are a lot of new permissions that you need to give which are newer to you. So when you create a security role from scratch and assign to a user you get so many errors.(Privilege)

The best thing to do here to copy a system create security role and then change the user privileges. This would let you work perfectly.

CRM 2011 Error - Principal user is missing prvReadSystemForm privilege

When you create a new security role from scratch and then assign only that role to a system user and when you log to the CRM site you might get the above mentioned error.

This is because you haven't given read permission to the Form in the Customization entity.

Once this is done the system would start working for you.

CRM 2011 Error - Principal user is missing prvReadQuery privilege

When you create a new security role from scratch and then assign only that role to a system user and when you log to the CRM site you might get the above mentioned error.

This is because you haven't given read permission to the View in the Customization entity.

Once this is done the system would start working for you.

Permisson Issue

Earlier today i post a link for checking permissions.

Below I'm giving the link which should be referred to identify which permission is lacking for the user.

http://support.microsoft.com/kb/953962