2011 User's Guide Copyright

səhifə	164/177
tarix	18.07.2016
ölçüsü	3.76 Mb.

1 ... 160 161 162 163 164 165 166 167 ... 177

Add or edit a sub-grid

To add a sub-grid, on the Insert tab, click the Sub-Grid button.

- OR -

To edit an existing sub-grid, click it, and then on the Home tab, in the Edit group, click the Change Properties button.

In the Sub-Grid Properties dialog box, on the Display tab, pay particular attention to the following fields:

In the Name text box, enter a unique name. This can only contain alphanumeric characters and underscore.
In the Data Source section, use the Entity and Default View lists to specify the group of records that you want displayed in the sub-grid.
If you want to edit the view that you selected, click Edit. To create a new view, click New. More information: Create or edit a system view for an entity

On the Formatting tab, click the options for the number of columns and rows to display in the sub-grid.
Click OK.

Add or Edit a Web Resource

Add or edit an image Web resource

Add or edit a text Web resource

Add or edit a Silverlight Web resource

Add or edit a Web resource for a form

Entity Relationships

Microsoft Dynamics CRM supports the following types of relationships between entities:

Hierarchical Relationships
N:N (Many-to-Many) Relationships
Self-Referential Relationships

A hierarchical relationship allows each child record to store a reference to one parent record. A parent record can be referenced by an unlimited number of child records. The parent record can display all the child records in an associated view.

Hierarchical relationships provide opportunities to configure a number of behaviors that affect data integrity and the business rules in your organization. There are also limitations on the types of relationships that you can create. More information: Understanding Hierarchical Entity Relationships (on page 572)

A 1:N Relationship is created or viewed from the primary entity. Any one record from the primary entity can be referenced by many records from the related entity.

A N:1 Relationship is created or viewed from the related entity. Many records from the related entity can reference any one record from the primary entity.

N:N (Many-to-Many) Relationships

N:N (Many-to-Many) relationships are not hierarchical because a record does not store a unique reference to another record. An N:N relationship allows reciprocally relating one or more records of an entity to a record of another entity. Also, an N:N relationship may be self-referential, meaning reciprocally relating one or more records of an entity to a record in the same entity.

Users who are associated with a security role that allows Read and Append privileges to one entity and Read, Write, and Append To privileges to another entity can relate records using this relationship.

Self-Referential Relationships

Both hierarchical relationships and N:N relationships can be self-referential. This means that an entity can have a relationship with itself. This permits records to be directly associated with other records of the same type. For example, opportunities can be linked to related opportunities.

The only limitation to self-referential relationships is that records cannot be related to themselves in a parental relationship. This would create a circular reference.

Understanding Hierarchical Entity Relationships

Hierarchical entity relationships require that one of the records have a field to store a unique identifier that references another record. The record that stores the reference to another record is called the child record. The record referenced by the unique identifier in the child record is called the parent record.

Data Integrity

A hierarchical relationship introduces the opportunity to define rules for data integrity. For example, an opportunity record has no meaning if it isn't associated with a customer record. Microsoft Dynamics CRM requires that an opportunity record be related to a customer record. However, a task activity can be meaningful whether it is associated to another record or not. Relating a task activity to another record is optional.

When you create a relationship, you must choose whether to enforce rules for data integrity. If you make the relationship field on the related entity required by setting a requirement level of Business Required, you can guarantee that each of the related entity records created through the Microsoft Dynamics CRM application will be related to a record of the parent entity.

Defining Relationships

Relationships are defined between entities. The entity that will represent the child records is called the related entity. A relationship attribute, also known as a lookup attribute, is created on the related entity to allow records to store a reference to a parent record. The entity that represents the parent records is called the primary entity in the relationship.

A 1:N Relationship is created or viewed from the primary entity. Any one record from the primary entity can be referenced by many records from the related entity.