Dataverse bulk delete adds permanent deletion and sandbox mode
Diesen Beitrag auf Deutsch lesen
New Dataverse bulk delete options support permanent deletion and sandbox execution through the Web API, with error details and restore controls also available.
TL;DR
Dataverse bulk delete jobs now support permanent deletion through CanRecoverDeletedRecords and sandbox execution through RunJobForSandbox in the Web API. Both options together reduced an example 1,100-record job to an average of 05:54, while individual results varied. The new settings are not yet available in the .NET SDK.
Original by Mark Carrington, on markcarrington.dev. Read the original
This is our own summary, not a republication or full translation.
Why it matters
- Makers: Use sandbox mode for disposable test data when plugins and related processing should not fire, but create the job through the Web API because the setting is not exposed in the UI.
- Admins/IT: Review whether permanent deletion fits retention requirements, remembering it matters when Keep deleted Dataverse records is enabled and removes restore options.
- BI/Data teams: Test both options against representative workloads, because the reported timing varied and sandbox mode alone was slower in the example.
Frequently asked questions
How do I enable permanent deletion in a Dataverse bulk delete job?
Set CanRecoverDeletedRecords to false in the Web API Options object. The permanent deletion checkbox appears only when Keep deleted Dataverse records is enabled.
How can I run a Dataverse bulk delete job in sandbox mode?
Set RunJobForSandbox to true in the Web API Options object. Sandbox mode is currently unavailable in the Dataverse bulk delete UI.
What happened to bulk delete failures in the Dataverse interface?
Failed records are logged in the bulkdeletefailure table and surfaced under Run details. The author could see counts, but the UI did not render details correctly.