Keeping Dataverse at a low capacity usage can be challenging, but it's crucial to avoid extra costs and headaches. Today I'm going to talk about a table that was consuming over 40k GB of our database: msdyn_documentsectionBase (a.k.a. Document Section).
There's not much documentation about these tables, just a reference to them as system tables, but since they have a direct relationship with the Project table, we were concerned about deleting these records directly.
After contacting Microsoft, that's what they said:
The msdyn_documentsectionBase table is used to store snaphots of the mpp file backing the work breakdown structure seen in the Task tab of the project form.
It is taking so much space because in order to faciliate recovery, we generally store backups of the project file for up to 30 days in this table. Whenever a user navigates to the tasks tab of a project, we automatically purge all snaphots older than 30 days.
If a projects schedule has seen a lot of edits in a short period of time, and then is never edited again, it is possible for backups related to that project to never be cleaned up.
That last part explains why it was taking up so much space and not being purged after 30 days.
Luckily, Microsft recently released a new API that allows the manual cleaning of this table. It's called msdyn_DeleteRecoveryDataForPCS. It can be called in Power Automate using Perform a bound action:
As of the publication of this post, there's no official documentation released for this API, but here's some clarifications from Microsoft:
We have confirmation from the product group team that DataWipeDate acts as on or before filter to wipe the data before that date.
(…) the product group team has confirmed that the API is designed to ensure that at least one record is retained to prevent any disruptions to the project. For instance, if you provide today's date and request to wipe everything, the API will make sure to keep at least one record intact to avoid breaking the project.
I hope that helps someone save some space in their database.
Don't stop learning!