Before going through the details of each one of above There is a common column in ( 1:N & N:1 ) Relationship Known as Type Of Behavior.there are 4 Type of Behaviours .
1. Parental : In this type of relationship Behavior , any action taken on the parent record is also taken on the child entity record. For example if the parent record is shared with a user, all the child records will also be shared with the same user.
2. Referential : In this type of relationship Behavior, the action taken on the parent entity record will not impact the child entity record
3. Restrict Delete : In this type of relationship Behavior, the action taken on the parent record will not impact the child entity record but you cannot delete the parent record until the child record exists
4. Configurable Cascading : In this type of relationship Behavior , The Configurable cascading allows the user to choose the Behavior they want to be apply. Below are the behaviors that can be configured:
Cascade All : This Behavior performs an action on all the related child records. For example if my opportunity is assigned to an another user then all the child records should be assigned to the same user
Cascade None : This Behavior performs no action on the child records
Cascade Active : This behavior performs action only on the active records
Cascade User : owned – This behavior performs action on the child records which are owned by the same user as parent
Remove Link : This behavior only removes the link for the child record without modifying anything on the record.
ONE TO MANY ( 1:N ) Relationship
This can be created manually and also created automatically on creation of lookup field to child entity of parent entity.
” Any one entity instance from the primary entity can be referenced by many entity instances from the related entity. “
This also create an navigation panel when we click on display option and can provide default plural name or an Custom name .
Note: The navigation panel for 1:N will only be shown on primary entity.
MANY TO ONE ( N:1 ) Relationship
Example : Example : One entity has only one CreateOn field , Same CreateOn field can be in “N” no of Entities.
” Many entity instances from the related entity can reference any one entity instance from the primary entity. “
MANY TO MANY ( N:N ) Relationship
This is the most complicated Let Understand it by an practical.
” one or more other entity instances of the current entity can be related to an entity instance of the same entity “
Step-1 : Lets Create an N:N Relationship Between “Account” an “Teston” Entity.
Step-2 : Open an record from any of the entity ( “Account” an “Teston” )
Step-3 : Click on the related entity and click ” add an existing ” to relate that record to another entity record.
Step-4 : click on that account record to see if teston record has been related to account or not
means with out any lookup both entities are related , this helps a lot in making professional flows .
Hope it was helpfull , if any questions please comment below
SOURCE : JUST2CODE.IN
Subscribe to our YouTube channel : https://www.youtube.com/user/TheRussell2012
One comment
Vishal Kumar
October 23, 2016 at 12:17 pm
Great work…!!!
Comments are closed.