Delete data in bulk
Unsure about entity vs. table? See Developers: Understand terminology in Microsoft Dataverse.
The bulk deletion feature helps you to maintain data quality and manage the consumption of system storage in Microsoft Dataverse by deleting data that you no longer need. For example, you can delete the following data in bulk:
Data that is irrelevant to the business.
Unneeded test or sample data.
Data that is incorrectly imported from other systems.
With bulk deletion, you can perform the following operations:
Delete data across multiple tables.
Delete records for a specified table.
Receive email notifications when a bulk deletion finishes.
Delete data periodically.
Schedule the start time of a recurring bulk delete.
Retrieve the information about the failures that occurred during a bulk deletion.
Run bulk delete
To delete data in bulk, you have to submit a bulk delete job by using the BulkDeleteRequest message. The bulk delete job runs asynchronously in the background without blocking other activities. The query expressions that describe the records on which to run the bulk delete job are specified in the QuerySet property of this request.
A bulk delete job is represented by the bulk delete operation table. The schema name for this table is
BulkDeleteOperation. A bulk delete operation record includes the following information:
Number of records that the bulk delete job deleted.
Number of records that the bulk delete job failed to delete.
Whether the bulk delete job is a recurring job or not.
Start time of the bulk delete job.
A bulk delete job only deletes records that are created before the job starts to run.
If a bulk delete job fails or ends prematurely, any records that were deleted before the failure or ending of the job are not rolled back and remain deleted. The failures of the
BulkDeleteOperation are stored in the
BulkDeleteFailure records and can be retrieved by using the RetrieveRequest message or the RetrieveMultipleRequest message.
A bulk delete job deletes the specified records according to the cascading rules. These rules are based on the relationship type between the tables. For more information, see Table Relationship Behavior.
To run a bulk delete job, a user must have the
Delete privileges for the table types being deleted. The user must also have read permissions to the table records that are specified in the BulkDeleteRequest message. By default, a system administrator has the necessary permissions; however, other users must be granted these permissions.
You can perform a bulk deletion on all tables that are supported by the delete action. For information about possible actions on table records, see Actions on table records.
If a plug-in or a workflow (process) is triggered by the delete action on a specific table type, it is triggered every time that a table record of this type is deleted by the bulk delete job.
Look at the following Organization service samples for the bulk delete feature:
Submit and view feedback for