当前位置：网站首页>Dynamics crm: relationships (1) - 1:n, n:1

Dynamics crm: relationships (1) - 1:n, n:1

2022-07-22 07:40:00 【Stone-hdj】

1:N and N:1 It can be understood as a positive and negative relationship , The quickest way to implement this relationship is to create a lookup Field （ Here's the picture ）, Target record type (Target Record Type) Yes. lookup The entity of . In the following example ,Account The entity plays N, and Guest Profile That is to say contact What the entity plays is 1;

So you're account The entity's N:1 Relationships This relationship can be found in

And in the Guest Profile(Contact) In the entity , It exists in 1:N Relationships in ：

How to create 1:N or N:1 Relationship

If we have two custom entities A,B, We want to be in the physical A Create pairs of entities in B Of 1:N Relationship

In entity A Of 1:N Relationships New China ：

  Or in an entity B Of N:1 Relationships New China ：

If we're in an entity A Create and entity in B Of 1:N Relations are as follows ：

  For the function of each field in the figure above , Please see the table below ：

Note: The parent in the following table , The parent record refers to Primary Entity, Children and child records refer to Related Entity.

Relationship DefinitionPrimary Entity Because we are really A Created in the 1:N The relationship between , So the main entity is EntityA
Related Entity Is the entity we want to associate B, When we choose EntityB after , Below Name The fields will be pre populated
Name In choosing Related Entity after , This field will be pre populated , And this field can only be changed at the time of creation , After creation, this field cannot be changed
Searchable

This option defaults to “ yes”. take searchable Set to no Will be removed from the options available in advanced discovery .

In this case, it will be an entity B The entity cannot be seen in the associated entity of advanced search A.

Hierarchical Here we can define hierarchical relationships
Lookup FieldDisplay Name The name will default to the name of the primary entity . This means that I will be in the entity B Provide a lookup field on , The user will see a file named EntityA Field of . however , if necessary , You can change this name .
Name This is what will be displayed in the entity B Upper Lookup Name of field . In this case , This is a “ new_EntityAId”. The name can be changed when creating the relationship , But once created , Can't change .
Field Requirement Like any field , I can set the lookup to optional (Optional)、 Business needs (Business Required) Or recommended by the business (Business Recommanded).
Description Text description . This has no effect on the function , But when the user hovers over this field , It will be displayed to the user .
Navigation Pane Item for Primary EntityDisplay Option

This will default to “ Use plural names ”(Use Plural Name). in other words , I EntityA There will be a name in the navigation EntityB The option to .

Custom Label If you choose   Use custom tags   As Display options , You need to enter a custom label to use , Not plural names of related entities . This option is not available , Unless the display option is set to user-defined label .
Display Area-  Details ： Select this option to include navigation items in   public   In the group .
-  marketing ： Select this option to include navigation items in   marketing   In the group .
-  sales ： Select this option to include navigation items in   sales   In the group .
-  service ： Select this option to include navigation items in   service   In the group .
Display Order This number controls the position of the navigation item in the selected display area . The number range allowed is from 10,000 Start . Navigation pane items with lower values appear above other relationships with higher values .
Relationship BehaviorType of Behavior

The default value when creating a custom entity is Referential. Other options include Parental、 Referential, Restrict Delete and Configurable Cascading.

  • Parental signify , If the parent is assigned 、 Delete ( wait ) , Changes will be cascaded to all children . In my example , This means that if the account is deleted , The policy will be deleted . wait .
  • Referential, This means that changes are not cascading . In terms of deletion , This will mean deleting links between entities .
  • Referential, Restrict Delete, Essentially with Referential identical . Cannot delete record , If there is an association . In this case , If one EntityB Has been associated with a EntityA, So when you delete this EntityB An error will be reported when recording
  • Configurable Cascading, Selecting this option allows you to manually set the cascading logic for each option .( Distribute , share , Delete etc. ) For other types of behavior , Cascading option sets are read-only . But choosing this option will allow each to be controlled individually .
Assign

And Share、Unshare、 Reparent and Merge equally , The assignment has the following options available .

  • Cascade All, This change will apply to all sub records .
  • Cascade Active, This change will apply to all active Child record of ,inactive Your records will be ignored .
  • Cascade User Owned, Changes will be applied to all child records owned by the parent record owner .
  • Cascade None, Other records will not be affected
Reparent

This option is actually similar to share/assign. If the parent of the child record changes , This command is triggered . for example , If set to Cascade All, The owner of the newly allocated parent record will inherit the access to the child record . however , If set Cascade None, Then the new owner will not inherit access .

read-only , Unless “Type of Behavior” I chose Configurable Cascading

Share read-only , Unless “Type of Behavior” I chose Configurable Cascading
Delete

read-only , Unless “Type of Behavior” I chose Configurable Cascading

Delete There is a different set of cascading options , These include ;

  • Cascade all,  Deleting a parent deletes all children . In this case , If there is one EntityA The record has been associated with EntityB in , At this time, if you delete this EntityA Recorded words , It's associated with EntityB These will also be deleted .
  • Remove Link, Deleting a parent record will keep all child records , However, the link in the child record linked with the parent record in the child record will be deleted .
  • Restrict, If you don't remove this association first , You will not be able to remove the parent record , Will report a mistake .
Unshare read-only , Unless “Type of Behavior” I chose Configurable Cascading

Merge

Defines if a parent record is merged with another parent record , Sub record what will happen

read-only , Unless “Type of Behavior” I chose Configurable Cascading

原网站

版权声明
本文为[Stone-hdj]所创，转载请带上原文链接，感谢
https://yzsam.com/2022/203/202207211547478402.html

边栏推荐

猜你喜欢

随机推荐