You’re offline. This is a read only version of the page.
46
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
I believe I understand what you are trying to say here.
Just to conclude, if in general you want that all opportunities are not re-assigned when assigning an account:
you should make sure that ALL relationships are set to Cascade None
Hi Jeroen,
Yes, I understand your example. With your example, if you see, there is a relations for potential custom which is set to cascade all. So if you assign any account which is populated as Potential Customer on the opportunity then this opportunity will also reassign. If that account is added to opportunity as Account or Partner only (and not potential Customer) then the opportunity will not reassign.
Hope this helps.
Hi Ravi,
thank you for your reply.
I am not sure if I understand it correctly so maybe I should specify my example a bit more:
1 to N relations on the Account entity
Entity Related Entity Field Type of Behavior Assign setting
Account Opportunity Partner (MSA field) Referential, Restrict Delete Cascade None
Account Opportunity Account Referential Cascade None
Account Opportunity Potential Customer Parental Cascade All
As you know, or perhaps know, these field are OOB if you also install PSA and FS.
With the current setup, if I would re-assign the Account, the opportunity will also be re-assigned to the new user.
So you could say, the working of this is, it will pick the most "open one" which is cascade all
or you could say, the working would be it will pick the most "restrictive" which his cascade None
I hope my example will make my issue or question a bit more clear.
REgards
Jeroen
Hi,
Each relationship will have its on cascading behaviour. So if you have 2 fields Account & Potential Customer on opportunity and Account is set to cascade all on Assign then when you assign an account record, it will also reassign all the related opportunity where this account is added as an Account (not Potential Customer). On a contrary, if you have cascading none set for Potential Customer then when you assign this account, it won't reassign the related opportunity where it is added as Potential Customer however it is possible that this record is added as an Account for some opportunities so for them it will reassign the opportunity records.
Regarding your second questions, it is possible that you see some changes in the behaviour after installing these solution as these may create some more relationship which may act as mentioned above.
Hope this helps.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (