Dataverse icon

Dataverse

Consume Microsoft Dataverse API
Join our community

Actions5

Overview

This node interacts with Microsoft Dataverse to manage entity records. Specifically, the "Delete" operation for the "Entity Record" resource allows users to delete a specific record from a given entity table by providing its unique identifier (GUID). This is useful in scenarios where you need to programmatically remove outdated or incorrect data entries from your Dataverse environment.

Practical examples include:

  • Automatically deleting customer records that are no longer active.
  • Removing test or temporary data after processing.
  • Cleaning up related records as part of a workflow automation.

Properties

Name Meaning
Entity Table Name The logical name of the entity table from which the record will be deleted (e.g., accounts).
Record ID The unique identifier (GUID) of the record to delete.

Output

The output JSON contains a confirmation of the deletion operation with two fields:

  • success: A boolean indicating whether the deletion was successful (true).
  • recordId: The GUID of the record that was deleted.

Example output JSON:

{
  "success": true,
  "recordId": "00000000-0000-0000-0000-000000000000"
}

No binary data is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with Microsoft Dataverse.
  • The node uses the Microsoft Dataverse REST API endpoints.
  • Proper permissions on the Dataverse environment to delete records in the specified entity table are necessary.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Record ID will result in an error because the record cannot be found.
    • Insufficient permissions to delete records in the specified entity table.
    • Incorrect Entity Table Name may cause the API to fail or return errors.
    • Network or authentication failures when connecting to the Dataverse API.

  • Error messages and resolutions:

    • "Record not found" — Verify the Record ID and ensure it exists in the specified entity table.
    • "Unauthorized" or "Access denied" — Check that the API credentials have delete permissions for the target entity.
    • "Invalid entity name" — Confirm the logical name of the entity table is correct.
    • If the node throws an error and the workflow is set to continue on failure, the error message will be included in the output JSON under an error field.

Links and References

Discussion