Monday, August 29, 2016

Minimum Privileges required to access MS CRM

When signing in to Microsoft Dynamics CRM:

1. To render the home page, assign the following privileges on the Customization tab: Read Web
Resource, Read Customizations.

2. To render an entity grid (that is, to view lists of records and other data): Read privilege on the entity, Read User Settings on the Business Management tab, and Read View on the Customization tab.

3. To view single entities in detail: Read privilege on the entity, Read System Form on the Customization tab, Create and Read User Entity UI Settings on the Core Records tab. 

Owner Team Vs Access Team in MS CRM

Owner Team:


1. We can grant security roles to owner teams.
2. Owner Team owns the record, i.e Owner field of each record will be filled with the team.
3. Need to be created manually or programmatically created and managed.
4. Will be cached in Dynamics CRM Server when user accesses application.
5. Can act as a resource in service scheduling.


Access Team;

1. We cannot grant security roles to access teams.
2. It cannot own any records.
3. Won't be displayed in most team views.
4. Can be system managed, directly from the form of the record that it relates to
5. Won't be cached as it doesn't derive privilege or ownership checks
6. Can't be scheduled as a resource in service scheduling

Tuesday, May 3, 2016

Things you might not know about solutions in MS CRM

Though we are working with the system very closely, certainly there are few things which we might not know.

Here I would like to give few important points related to solutions.


  • You can’t export your default solution as a managed solution
  • MS CRM don’t support importing a default solution taken from an on-premise deployment into a CRM Online organization or a default solution taken from a CRM Online organization into an on-premises deployment. MS CRM do support importing custom solutions between these deployment types, but not default solutions
  • When you export a managed solution, you can’t import it back into the organization it was imported from
  • All imported security roles will be attached to the root business unit
  • If you import customizations that include a language that is not installed on your system, any labels defined in the customizations will default to the base language of the Microsoft Dynamics CRM system the customizations were imported from.

These are very interesting points I came to know when I gone through MS CRM adminstration guide. Please comment if I miss any so that those points will be added to the list.

Monday, May 2, 2016

Minimum privileges for common tasks in MS CRM

1. When logging in to Microsoft Dynamics CRM:


  • To render the home page, assign the following privileges on the Customization tab: Read Web Resource, Read Customizations
  • To render an entity grid (that is, to view lists of records and other data): Read privilege on the entity, Read User Settings on the Business Management tab, and Read View on the Customization tab
  • To view single entities in detail: Read privilege on the entity, Read System Form on the Customization tab, Create and Read User Entity UI Settings on the Core Records tab

2. When logging in to Dynamics CRM for Outlook:

  • To render navigation for Microsoft Dynamics CRM and all Microsoft Dynamics CRM buttons: Read Entity and Read View on the Customizations tab
  • To render an entity grid: Read privilege on the entity, Read Customizations and Read Web Resource on the Customization tab, and Read Saved View on the Core Records tab
  • To render entities: Read privilege on the entity, Read System Form on the Customization tab, and Create, Read, and Write User Entity UI Settings on the Core Records tab

Tuesday, March 8, 2016

Paging with FetchXML

In MS CRM 2016 on-premises and online, fetchXML came up with a new attribute called “page”. Using this attribute we can set which page results we want.

<fetch mapping="logical" page="1" count="2">
 <entity name="account">
  <attribute name="accountid" />
  <attribute name="name" />
  <order attribute="name" />
 </entity>

</fetch>

Above query set query for accounts and limit the number of entities to 2 and return just the first page.


Friday, March 4, 2016

date and time field behavior in MS CRM

For CRM versions earlier than CRM Online 2015 Update 1 and CRM 2016 (on-premises), you cannot define the behavior of the date and time values. By default, the date and time values are stored as  UserLocal.

But in latest version,  behavior of date and time field is classified as 3 types.




UserLocal:
·         This behavior always stores the date and time in UTC format. While retrieving, it will returns date and time in UTC format.
·         When user trying to update date and time, if user enters date in UTC, system will update the value as it is or else it will convert entered date and time into UTC format then stores.
·         This behavior is used for system attributes like CreatedOn and ModifiedOn, and cannot be changed. You should use this behavior for custom attributes where you want to store date and time values with the time zone information
DateOnly:
·         This behavior will stores date only and time will be always stores as 12:00AM (00:00:00).
·         While retrieving the value also, time will always carries as 12:00AM.
·         This behavior should be used for custom attributes that store birthdays and anniversaries, where the time information is not required

TimeZoneIndependent:
·         Stores the date and time in system regardless of user time zone.
·         While updating the date and time also, it will stores date and time what user enters as it is.


·         This behavior should be used for attributes that store information such as check in and check out time for hotel

If you do not specify the behavior while creating a date and time attribute, the attribute is created with the UserLocal behavior by default



You may like below posts

Improving MS CRM Performance

Performance Center in MS CRM 2013

Upsert in MSCRM

Locking mechanism in MS CRM

Ticker Symbol Field in MS CRM

Themes in MS CRM

Enable Tracing in MS CRM

Calculated Field in Dynamics CRM 2015

IME Mode in MS CRM

Date and Time field in MS CRM

Date and Time fields generally are meant to store date and time. Did you ever tested, what is the max early date you can give in that field?


If not, try with 12/31/1899 if you are using MS CRM 2015 on premises with update 1 or earlier version. And, you will get an error as “The specified date format is invalid or the date is out of valid range”. Because maximum early date you can give is 1/1/1900 or later


Now, MS CRM easing this restriction in MS CRM 2015 online with update 1 or 2016 on-premises. In these versions, you can give date as early as “1/1/1753 12:00 AM



You may like below posts

Improving MS CRM Performance

Performance Center in MS CRM 2013

date and time field behavior in MS CRM

Upsert in MSCRM

Locking mechanism in MS CRM

Ticker Symbol Field in MS CRM

Themes in MS CRM

Enable Tracing in MS CRM

Calculated Field in Dynamics CRM 2015

IME Mode in MS CRM