Applies to Product - Microsoft Dataverse
What’s happening?
Some accounts exhibit an improper sharing history, displaying users who previously had access to records, even though they no longer do. This issue is inconsistent and affects only specific accounts.
Reason:
The underlying cause appears to be related to the product's behavior, specifically how the Principal Object Access (POA) table manages shared records between users and teams. The access rights for users may not be accurately reflected in the system interface.
Resolution:
- Assign Basic User Role: Temporarily assign a basic user role to the affected user. This refreshes their role and may allow for the removal of shared access.
- Revoke Access: Follow the documentation on revoking access for sharing. The relevant document can be found at Microsoft Learn.
- Check POA Table: Validate that the share has been completely removed from the POA table. If the record does not exist in the POA table, the view for checking access should not show the user.
- Testing: Conduct tests to ensure that the expected behavior occurs. If the user still appears in the sharing history after access has been revoked, further investigation is needed to determine if the issue is due to incorrect actions taken or an error during the revocation process.
- Follow-Up: If the issue persists, gather additional information from the customer regarding the specific records affected and any child records associated with them. This may help in understanding the cascading behavior of access permissions.
- Documentation Review: Review the documentation on known issues and limitations related to the Power Apps grid control, as this may provide insights into the behavior observed.