Hi Tsvet,
Just to confirm, in the screenshot you posted, are you looking at the Account/Lead relationship or Contact/Lead relationship (both via the customerid field)? The Description field makes it look like the Contact/Lead relationship. I just want to confirm you're checking the appropriate relationship in each environment. Does your Account/Lead relationship look like this?
If so, and the cascading behaviour is the same in production and staging but you're getting different results, something else must be at play here.
Can you reproduce the issue with as many other variables removed, so for example are you testing with the same users in both environments, or at least do the users have the same security roles? Could a workflow or plugin be changing the ownership back? If you have audit enabled on the Lead entity, check the audit log so see if ownership changes are happening as expected in both environments.
I hope this is of some help! By all means, post back with your findings.
------------------------------
Andrew Bibby
Dynamics 365 Consultant & Project Advisor
Evesham, United Kingdom
------------------------------
Original Message:
Sent: Jul 24, 2019 12:21 AM
From: Tsvet Tsonevski
Subject: Cascading Rules Account to Lead
We are on Dynamics 365 online and I just noticed that the cascading rules Account to Lead don't work in the staging environment. When I change Account owner the related Contact owner changes, the open Opportunity follows (we keep closed opportunities outside the cascading rules), but the Lead owner doesn't change. I reviewed the cascading rules in the Account's 1:N Relationships and regarding parenting Account-Lead they are set to 'Cascade All". Interestingly, the production environment works just fine with the same "Cascade All" settings in the Account-Lead 1:N Relationship.
What am I missing? Is it possible something else is affecting the cascading rules that I am unaware?
------------------------------
Tsvet Tsonevski
------------------------------