Ana səhifə

2011 User's Guide Copyright


Yüklə 3.76 Mb.
səhifə166/177
tarix18.07.2016
ölçüsü3.76 Mb.
1   ...   162   163   164   165   166   167   168   169   ...   177

Create or edit N:1 relationships between entities


Can I do this task?

This task requires the System Administrator or System Customizer security role or equivalent permissions. Customization tasks can be performed only while you are online. More information: Customization Permissions (on page 474)

A N:1 relationship is a hierarchical relationship. More information: Understanding Hierarchical Entity Relationships (on page 572)


  1. In the Navigation Pane, click Settings.

  2. Under Customization, click Customizations.

  3. In the Customization area, click Customize the System.

  4. Under Components, expand Entities, and then expand the entity you want.

  5. Click N:1 Relationships.

  6. To edit a relationship or view the details for a relationship, select the relationship, and on the Actions toolbar, click Actions, and then click Edit.

- OR -To add a new relationship, click the New Many-to-1 Relationship button.

  1. For a new relationship, in the Relationship Definition section, select the Primary Entity. A default Name value will be added after you select the Primary Entity. You can accept this name or enter a new one.

Note

If you change the Primary Entity before you save, the value of the Name field will not change. Make sure that this value is meaningful before you save.



  1. In the Lookup Field section, for a new relationship, enter information in the following fields:

  • Display Name

  • Name

  • In the Requirement Level list, you can choose one of the following options:

  • No Constraint

  • Business Required

  • Business Recommended

  1. In the Navigation Pane Item for Primary Entity section, in the Display Option list, you can choose one of the following options:

  • Use Plural Name

  • Use Custom Label

  • Do Not Display

When the Use Plural Name or Use Custom Label options are selected you can choose from the Display Area field to specify where the relationship label will be displayed on the form. You can also specify the Display Order to control where the label will be included within the selected display area. The range of allowed numbers begins with 10,000. Relationships with a lower Display Order value will appear above other relationships with a higher value.

  1. In the Relationship Behavior section, for new relationships and for existing relationships with Type of Behavior set to Parental, you can choose the type of relationship.

What happens when you take an action on this entity is defined by the type of relationship. For Parental, Referential, and Referential, Restrict Delete, the specific behaviors are determined by the relationship type. For Configurable Cascading, you must select the behavior you want for each possible action.

  1. In the Type of Behavior list you can choose one of the following relationship types:

  • Parental

  • Referential

  • Referential, Restrict Delete

  • Configurable Cascading

  1. If you selected the Configurable Cascading relationship type, for each of the six actions listed below, you can select the behavior for the action.

If you set all the behaviors for the actions to match the behaviors for the actions for the other relationship types, when you save the relationship, the type of behavior is automatically set to the other type. For example, if you set all the actions to Cascade All, the relationship type is changed from Configurable Cascading to Parental.

  • Assign

  • Share

  • Unshare

  • Reparent

  • Delete

  • Merge

The behaviors for these actions include:

  • Cascade All

  • Cascade None

  • Cascade Active

  • Cascade User-Owned

  • Remove Link

  1. Click Save and Close to close the Relationship form.

  2. When your customizations are complete, publish them:

  • To publish customizations for only the component that you are currently editing, on the Home tab, in the Save group, click Publish.

  • To publish customizations for all unpublished components at one time, click Publish All Customizations.

Notes

  • A custom entity cannot be the primary entity in a relationship with a related system entity that cascades. This means you cannot have a relationship with any action set to Cascade All, Cascade Active, or Cascade User-Owned between a primary custom entity and a related system entity.

  • No new relationship can have any action set to Cascade All, Cascade Active, or Cascade User-Owned if the related entity in that relationship already exists as a related entity in another relationship that has any action set to Cascade All, Cascade Active, or Cascade User-Owned. This avoids relationships that create a multi-parent relationship.

  • Any time you change user interface elements or implement form scripts for an entity, you must publish changes to apply them. Any customizations that change the data schema of Microsoft Dynamics CRM such as custom entities, relationships, or fields are applied immediately.

Related Topics


Understanding Hierarchical Entity Relationships 572

Understanding Entities 499





1   ...   162   163   164   165   166   167   168   169   ...   177


Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©atelim.com 2016
rəhbərliyinə müraciət