New Design

Recent Post

Thursday, August 29, 2013
no image

MSCRM - Creating a Check-Box


1. Create a new field, select the type as 'Two Options', by default you will get the values of 'Yes and No', customize them if you want. save and close the field.
2. Drag the field to the form and place it on one of the placeholders, at your own desired location.
3. Double click on the field, and the field properties window should open.
4. In field properties go to the formatting tab.
5. There you will see a 'control formatting' drop down, (by default its value will be 'Two Radio Buttons' )
from that drop down, select the 'check box'.
6. Save and Publish, you should now have a checkbox on your form.
Friday, August 16, 2013
no image

MSCRM - Modify the Parent & Child relationship

Parent & Child relationship of Entities should be well defined at the beginning. If you want to change the entity relationship after data imported to the system, you will find that the relationship of existing records do not automatically re-build as using the new definition.

To resolve this issue, you can using the re-parent setting to re-assign the owner of each records. But if the volume of data is huge, you want to die......

So, another approach is updating the database directly. (But it is an unsupported solution from Microsoft, you need to take your risk!!!)

Example,
You want to remove the Account & Contact Parent & Child Inherited relationship, you need to update the table: (assumed you have already changed the Account & Contact relationship setting to "Cascade none")

update PrincipalObjectAccess
set InheritedAccessRightsMask = 0
where ObjectId in (select contactid from ContactBase)



Thursday, August 15, 2013
no image

MSCRM - Entity Relationship Q&A

Question: Cannot edit Merge and Delete behavior in 1:N entity relationship

In 1:N relationship of Account entity, the delete and merge behaviors appear as 'Cascade All'. Both option sets are read-only and I cannot modify it.

Please advise why is that and how can I modify these behaviors.

Answer:
The Merge behavior never can be edited, it is a CRM restriction. This value is always "Cascade All" in the 1..N relationships from Account, Contact and Lead, that are the only entities that allow merging. In other entities the value is always "Cascade None".

The Delete behavior can be edited. but not in every cases. In the case of Account this behavior can be edited only in 1..N custom relationships.

From : Dynamics
no image

MSCRM – Entity Relationships Explained

Definition

Entity Relationships is to define the data relationships between two entities in the system metadata.

Dynamics CRM design gives the flexibility to manage the data relationships thru the metadata without touching the underlying SQL database keys.

These settings can be managed within the entity form in the design mode.

Dynamics CRM supports basically supports 2 relationships between any two entities -
1: N and N:N

no image

MSCRM - Cascade Option on Relationships in Microsoft CRM

In MS CRM, an important relationship between the entities. The following I summarized and quoted from diff. sources to explain the relationships.

Applied to CRM 2011

Breaking News
Loading...
Quick Message
Press Esc to close
Copyright © 2013 Technology KB All Right Reserved