Applies to Product - Dynamics 365 Business Central
What’s happening?
Users are able to see records that have been reassigned to other individuals in Power Apps, despite the records being assigned to different users.
Reason:
This arises from the system not fully clearing the relevant records in the Principal Object Access (POA) table when relationships are modified. This results in some POA records being left behind, allowing users to retain access to records that they should no longer see.
Resolution:
What’s happening?
Users are able to see records that have been reassigned to other individuals in Power Apps, despite the records being assigned to different users.
Reason:
This arises from the system not fully clearing the relevant records in the Principal Object Access (POA) table when relationships are modified. This results in some POA records being left behind, allowing users to retain access to records that they should no longer see.
Resolution:
- Check all POA records related to the records in question.
- Use the RetrieveAccessOrigin API to determine if any POA records are orphaned. If the API returns the message: "Access origin could not be found. Access does not come from POA table or object ownership," it indicates that the record is orphaned.
- If orphaned records are found, utilize the ResetInheritedAccess API to delete these records.
- Review the asynchronous operations involved in the record creation and reassignment for affected tables to ensure they are functioning correctly and consider merging them into a single operation to prevent timing issues that may lead to this problem.