Dynamics Community Forum Thread Details

How to cleanup PrincipalObjectAccess (POA) using c# for MS D365 Online?

Hi,

Since you are using online CRM please raise request with Microsoft support for the cleanup. Also please read the below points which can be implemented from your end.

Best practice:

Share only what is needed

Limiting the amount of sharing that takes place we will reduce the total number of records in the POA table. If users frequently share records with other users, can benefit from setting teams as owners of those records or to have the users share with Teams instead of specific set of users. Share with teams, not users, and use access teams for controlling sharing.

Minimize the number of Business Units where possible

Helps reduce the need for sharing records

Ensure users are placed in the appropriate Business Unit

A user could maybe be moved further up the Business Unit hierarchy to give them the necessary access to records in another Business Unit

Modify Security to allow users to see information outside of their Business Unit

This will also reduce the need for sharing

Once a record does not need to be shared any longer, stop sharing it

Enable the EnableRetrieveMultipleOptimization registry key

Enabling this will cause the queries to make use of temp tables

Evaluate splitting TempDB out to its own physically separate RAID array

=======================================================

Should look to cleanup up the POA table using Bulk Delete operation.

The Bulk Delete job you would create is very similar to proactively maintaining the AsyncOperationBase table via Bulk Delete.

Go to Settings > Data Management > Bulk Record Deletion and click New.
Click Next, then on the Define Search Criteria page set the Look for selection to Process Sessions
Define the criteria for you Bulk Delete. For example, you could use Status Reason = Completed; Cancelled.
After defining your criteria, click Next to get to the Select Options page.
Provide a name, start time, and recurrence pattern, and then click Next.
Click Submit.

If a bulk delete job for Async Operations already exists, or for anything else, ensure that you do not schedule the jobs to run at the exact same time. For example, if you already have a Bulk Delete job that runs nightly, weekly, etc... at midnight; do not also schedule this one to run at midnight. Specify a different time such as 1:00 am instead.

https://support.microsoft.com/en-us/topic/performance-is-slow-if-the-asyncoperationbase-table-becomes-too-large-in-microsoft-dynamics-crm-334a0738-e132-1ea7-cab3-7fd68cb823a4

Quick Links

Subscribe to this forum!