Hi All,
I understand that the Relation Type of Behavior is determining how entities relate to each other and that you can setup what to do on the Assing, Share, Delete, etc. events.
Initially our system was setup that when you re-assign an Account, it does not change the owner of the related Contacts or Opportunities for example.
This means the Relationship Type Behavior for the Assign action was set to Cascade None.
Since a while some users reported that re-assigning of Accounts was also re-assigning related entities like Contacts or Opportunities.
So have two questions that I would like to ask the community :
1. Now I did notice there are more 1 : N relations from Account to Opportunity for example, you have the Account field but also Potential Customer field.
Can somebody explain or know how these behaviors work when you have multiple relations (1:N) to the same entity even though it is a different field ?
2. Did any one else had similar issues after installing Project Service Automation, VOC or Field Service perhaps ? (since we did not change this ourselves we believe)
That the relationship were working differently then expected? in our case on the re-assign event.
Kind regards,
Jeroen
