web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Answered

Change ownership of child records based on parent record automatically

(0) ShareShare
ReportReport
Posted on by 905

Hello,

I would like to know if the relationship behavior can achieve the below:


If a parent record owner is owner A, then all child records associated with the parent should be owned by owner A. So it inherits the owner assigned of the parent record.

The scenario I am doing is:

The parent record is created by me, as owner B, when I change the parent record ownership to Owner A, I don't want to manually change the related child records to Owner A as it should automatically change the assigned user to Owner A.

In order to accomplish the above, what is the best approach? Can you provide an example?

Any help is greatly appreciated.

Best regards,
EBMRay

I have the same question (0)
  • Verified answer
    HandeMV Profile Picture
    on at

    Hi,

    This can be handled by relationship behaviour.

    1. Open Solution and Navigate to Table(Entity) -> Select Relationship of your entities -> Relationship Behaviour.
    2. Change Relationship Behaviour Assign to Cadcade All. This will resolve your problem.

    pastedimage1683270134341v1.png

    Please mark it as verified if this solves your issue. 

  • Suggested answer
    Haig Liu Profile Picture
    Microsoft Employee on at

    Hi EBMRay,

    I guess what you want to find out is the cascade rule:

    https://ledgeviewpartners.com/blog/what-are-cascading-rules-in-microsoft-dynamics-365-crm/

  • EBMRay Profile Picture
    905 on at

    Hello HandeMV ,

    Thank you for providing the documentation.

    As per my testing, I have changed the relationship behavior to the following:

    pastedimage1683555012072v1.png

    Mainly, I have a table called equipment related to another table called equipment testing as 1:N.

    The simulation I did is:

    Struggling-Scenario.gif

    • I changed the current parent owner to the user desired before creating the parent record.
    • While creating the child records it always takes me as the current owner and does not reflect changes according to parent ownership.
    • However, when I change the parent owner to any other owner it reflects in the child records.

    What I am still struggling with:

    Scenario-2.gif

    It should always take the owner of the parent record when I create a child record even if I was a different owner than the parent record.

    Could you please advise what I am doing wrong? I appreciate it if you could provide an example.

    Thank you,
    EBMRay

  • Verified answer
    HandeMV Profile Picture
    on at

    Hi,

    Exactly, when we change parent record owner, relationships will update child records. If we are creating new child record manually, it always auto populated as user who is creating it.

    If you want to update even while creating, just write javascript on load of form and set Owner field of record as owner of parent record. Then you will always see parent owner in child owner.

    If you don't want it while creating it but as soon as you save it should reflect, then second approach would be, just create run time workflow on create of child record, set owner as owner of parent record. This would be simple approach if you don't want it while creating record.

    If you still have doubts just let me know.

  • EBMRay Profile Picture
    905 on at

    Hello HandeMV ,

    Thank you for your reply.

    So the only way will be to have a JS/Plugin/Workflow to set the Owner based on the parent record.

    The main pain of this problem is that I have around 196 tables related to that parent entity so I will have to add those JS to all the forms right?

    Appreciate your support.

    Best regards,

    EBMRay

  • Suggested answer
    HandeMV Profile Picture
    on at

    You have to add it. I would say if you have that many, just create a single plugin which updates current record based on parent and add plugin step for all entities. So there won't be duplicate and you don't need to write it again and again for each entity.

    Please mark this as verified if it resolves your issue.

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.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
Siv Sagar Profile Picture

Siv Sagar 93 Super User 2025 Season 2

#2
#ManoVerse Profile Picture

#ManoVerse 80

#3
Martin Dráb Profile Picture

Martin Dráb 64 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans