Friday, March 9, 2012

Security Model in CRM 2011

There are 3 ways we have the security level in CRM.

  • Role Based
  • Record Based
  • Field Based
Microsoft have written a very good article on this. This can be views at the following link.

Field Level Security with CRM 2011

This is a new feature which has been given with CRM 2011.
With earlier versions we had to write java scripts for hiding of fields. This required checking the user has privileges and going on about it

With CRM 2011 we can do this using the field level security. We no longer have to write any java scripts for this.

However there is one thing. We can only use field level security with custom fields that we have created. Not with the system fields.

This contains a very good article on this.

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.

CRM 2011 Update Roll Up 6 Released

UR 6 for CRM 2011 has been released. This as usually have fixed a lot of issues and have added some additional enhancement to CRM. The new version is 05.00.9690.1992.

You can download this from the following location.

Retrieving Calendar of a Bookable Resource in Dynamics

There are occasions where we need to retrieve working days and working times of a resource in Dynamics grammatically. This is quite possible...