Publish / saas · All operations

Delete records in an application

A variant of Write to an application's API

Remove the application's records that match the input rows' keys.

Status

In arcform

Not built yet

arcform does not do this yet. Its place on the roadmap

What other tools call it

Meridian's classification; an independent blind rating agreed on 95.7% of 324 rows (variant, version 3).

Apache Hop (1)
Bruin (1)
  • deleteread 2026-09-27

    Remove matching remote records, soft or hard per destination

Pentaho Data Integration (2)
RapidMiner Studio (2)
Talend (1)

Background

In Bruin, the delete strategy removes the target application's records that match the source rows, through its application programming interface (API).[1] In Bruin, whether a delete is a soft delete that archives a record or a hard delete that removes it for good depends on the destination.[1]

When to use it

In Bruin, some APIs offer only a soft delete or only a hard delete.[1] Find out which kind of delete the application performs before the first run, and whether a soft-deleted record can still be found and restored. (Meridian's view) Mirror a source onto an application only when the source holds every record the application should keep, and send the keys of particular records to a delete when only those should go. (Meridian's view)

In RapidMiner's Delete Salesforce operator, unless skip invalid rows is selected, the process fails if a record cannot be deleted and reverts all previous deletions.[2] EasyMorph's Zendesk command can fail, warn or carry on silently when a ticket it is asked to delete does not exist.[3]

The method

Apache Hop's Salesforce Delete transform deletes records from Salesforce through the Salesforce Web Service, a batch of records at a time.[4] EasyMorph's Update/Delete records in Salesforce action deletes the records whose IDs are in a chosen column of the dataset.[5] In EasyMorph's Airtable action, a delete removes the Airtable rows whose row IDs match those in the EasyMorph table.[6] EasyMorph's SharePoint list action can delete only the rows whose IDs are in a column, or every row in the list.[7] Read the application's own record IDs back before a delete, rather than deleting by a field you only hope is unique. (Meridian's view)

In the Hypertext Transfer Protocol (HTTP), a DELETE request asks the server to remove the association between the target resource and its current functionality.[8] Under HTTP, whether a deleted resource's representations are destroyed and its storage reclaimed depends entirely on the resource and its implementation by the server.[8] An HTTP server that accepts a DELETE should answer 202 (Accepted) when the action will likely succeed but has not yet been enacted.[8]

Sources

  1. [1]Reverse ETL | Bruin CLIdocumentation
  2. [2]Delete Salesforce - Rapidminer Documentationdocumentation
  3. [3]ZENDESK COMMAND [EasyMorph Help]documentation
  4. [4]Salesforce Delete | Apache Hopdocumentation
  5. [5]UPDATE/DELETE RECORDS IN SALESFORCE [EasyMorph Help]documentation
  6. [6]UPDATE/DELETE ROWS IN AIRTABLE [EasyMorph Help]documentation
  7. [7]UPDATE/DELETE ROWS IN SHAREPOINT LIST [EasyMorph Help]documentation
  8. [8]RFC 9110: HTTP Semanticsstandard