We have facing issue from today where case is automatically changing ownership to service account. I checked one of the previous error on this forum and found something related to relationship but I can check and verify that my contact - case relationship is already as cascade none as specified.
Is there any troubleshooting we can do? I already checked and could verify that none of the flows are calling this as most of the cases (almost 99%) are resolved and there are no flows where they are triggered or anything.
Hi Kavish,
This is most likely due to the cascade setting of the relationship.
As you mentioned, you have checked contact, have you checked account?
Hello,
I have few questions, hopefully you could answer.
I was trying to think how relation between case and contact, case and account is affecting the owner which is entirely different
Can this cause any further repercussions.
We have these set to parental type behavior set. I am just trying to understand what changing it will do. And why it will work.
Hi,
If you see the definition of Parental relationship, it says any action take on parent record will take affect to child records too -
Parental
o In a parental relationship between two entities, any action taken on a record of the parent entity is also taken on any child entity records that are related to the parent entity record. if you delete a record in the parent entity, the related child entity records are also deleted; or if you share a parent entity record, the related records from the child entity are also shared. All option are disable for Parental relationship
We have 4 types of relationship behavior as given below.
Individual Behaviors
For Assign, Share, Unshare, and Reparent the options are:
For OOB relationship of account/contact and case, behavior type is Parental, default option of Assign behavior is Cascade All, which means that all the related cases are also assigned to the new account/contact owner when you assign the account/contact.
For more details, you can refer following link:
Entity relationship behavior (Developer Guide for Dynamics 365 Customer Engagement (on-premises)) | Microsoft Docs
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
MVP-Daniyal Khaleel 64
Tom_Gioielli 16 Super User 2025 Season 2
CU29080825-0 16