All Ideas

Idea Details

Post an Idea

This idea has been merged into another idea. To comment or vote on this idea, please visit The Apex Data Loader should support use of external IDs on UPDATEs.

0 Points voting closed

Open

Balu Sharma

Data Loader should support delete with External IDs

Data Import & Integration

Data Loader today only supports upsert with External Id. It would be useful, for full automation of data loading to support deletes as well with external id - today deletes can only be done with Salesforce Id.

· Flag

Comments ( 14 )

Sort By

Kevin Liu - 1 year ago

Need this function to improve our auto process
- Flag
Debarshi Roy - 1 year ago

Much needed when performing deletes using an ETL tool referencing an external Id.
- Flag
Pankaj Lokhande - 1 year ago

Much needed
- Flag
suresh kalluri - 1 year ago

Very much needed
- Flag
Glen De Marcos - 1 year ago

Nice to have to avoid workarounds
- Flag
Isha Bansal - 2 years ago

Will be nice to have
- Flag
rahul chandra - 5 years ago

Use upsert, update anything on the records. The success file will have Salesforce Ids, use it to delete them.
- Flag
ACF Solutions - 6 years ago

Yes please! I hope this will come soon.
- Flag
Dave Sommer - 7 years ago

i agree! sfdc should support delete using external id
- Flag
Robbie Piotrowski - 7 years ago

Seriously....tag it, pull it, then delete it? Or, pull everything, look up Ids, then delete? Can we get an admin to help design the next update?!
- Flag

Chris Noe - 8 years ago

It would be great if the API supported deletes using External Id fields. Saves a lot of round trips when we are trying to delete records from Salesforce using integration tools like Informatica where an external id from the source system is used on the Salesforce side.

Flag

Will Lee - 8 years ago

also to be able to use the external id in a foreign key relationship in another table.
- Flag
山崎　拓己 - 10 years ago

I want SFDC to come true by all means. I am really nonsense to do export for upsert.
- Flag

Balu Sharma - 11 years ago

The workaround is pretty ugly. To each object, you add a "deleted" field. You upsert records to be deleted with this field set as true. You extract the them back with a salesforce id using extract in Data Loader. You then delete them...