Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I want to cleanup or delete rows PrincipalObjectAccess (POA) using c# for MS D365 Online.
Can anyone tell me the steps how to do that using c#?
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.
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.
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.
You can also evaluate "SQL 4 CDS" with XRM toolbox and use the below reference support article to frame a clean up script.
Ensure that you run the deletion in small batches using meaningful filters to avoid excessive run duration.
Business Applications communities