Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I have an Account Account A, Account Owner = "Smith" and Custom Entity B.Relationship 1:N and Relationship Type is Configurable cascading.Assign, Share and Unshare = Cascade AllReparent = Cascade ActiveDelete = Remove LinkMerge = Cascade All
In custom entity B, I have 2 fields Owner and Sales representatives.
If any sales representative will create a new record in Custom entity B, he is the owner and he is the sales representative for his/her own records.Sales representative C and SalesRepresentative D are in the same business unit the same security roles and associated with Account A.Now one of my team members changes the Account A Owner to "Robin" in account entity.All the Owner of the associated record changes to "Robin" in custom entity B.
Now Sales representative C reports that he can't able to see his own records, but SalesRepresentative D can able to see his records without any issue.
Let me know what went wrong in this scenario, why the Sales representative C can't able to view his owned records in CRM.
I would first check to see if C and D have to same security roles
Yes, C and D are having same security roles
One possibility here is that D is a member of a Team that C is not, and the access is being granted to D that way. One option that you may be able to take here to mitigate the situation is to enable the "share reassigned records with original owner" setting within System Settings. If these details do not lead to a solution, I would look for clues in the PrincipalObjectAccess table to see if something else triggered a share to D that didn't happen for C.
Business Applications communities