Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
Many of you would be interested in finding out what’s driving storage consumption of you Dynamics 365 Customer Engagement instance. Some would think it’s largely data for entities, i.e. Account, Contact, Lead, Opportunity, Custom etc. Which is true to a large extent but with few exceptions. Organization database also holds system data linked with user records. House keeping such system data is handled by Deletion Service. This post on our CRM PFE Team site explains clean up by Deletion Service. If you are not familiar with Deletion Service, I suggest you read above post to put this altogether.
Now you know the role of Deletion Service, hopefully. Hey, I take that an assumption to continue writing . I was working with a customer to prepare for an upgrade and noticed some of the system data related tables were significant in size. While it came as surprise for customer their knowledge was claiming system data should be getting cleaned by the system(aka Deletion Service). So, started digging around the Deletion Service behavior for the organization in question. Deletion service executions were successful, no errors! Further going into the details of few large tables, it came to light that system data was retaining longer than usual. Found several OrgDBOrgSettings were set differently for this Org.
We could have restored to default values but chose to discuss retention requirements, general guidance and adjusted the settings accordingly. Once we adjusted these settings, next run of Deletion Service took care of reducing size of respective tables.
From above learning, here are the OrgDBOrgSettings those control Deletion Service retention along with description:
These settings can be retrieved updated using OrgDBOrgSettings command line tool described in this KB article or OrgDBOrgSettings Solution.
Hope this helps!
Business Applications communities