Replies: 6 comments 1 reply
-
Thank you for filing this feature request. We appreciate your feedback and will review the feature at our next grooming or sprint planning session. We prioritize feature requests with more upvotes and comments. |
Beta Was this translation helpful? Give feedback.
-
This issue has been linked to a new work item: W-12408034 |
Beta Was this translation helpful? Give feedback.
-
Hi @codeulike, sorry that this issue has been quiet. Does the |
Beta Was this translation helpful? Give feedback.
-
Thanks I'll have a look at |
Beta Was this translation helpful? Give feedback.
-
You asked what else would you like to see it report? Using version 2.1.7-355d833
for the 162 records that failed, I want to see the error message for each row. In the UI (for Bulk API 1) these are downloadable CSVs that give me this information: For Bulk API 1 the rest call to fetch the results CSV is documented here: https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/asynch_api_batches_get_results.htm For Bulk API 2 I think its this one: https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/get_job_failed_results.htm#get_job_failed_results Being able to get row-by-row results of what succeeded and what failed (and why) is very very useful in real world loading scenarios Many thanks |
Beta Was this translation helpful? Give feedback.
-
Hey @codeulike - I just finished testing these changes. Keep an eye out in the release notes for a new |
Beta Was this translation helpful? Give feedback.
-
force:data:bulk:upsert is a really convenient way to use the Salesforce bulk api
BUT there isn't a command to fetch the results once your job has finished, you have to go into the Salesforce UI and download them (batch by batch) or use some other method like the REST API to retrieve them
When doing a serious data import into Salesforce (several objects, hundreds of thousands of records etc) the Results of a Bulk API job are very important because:
a) for your successful rows, you want to know the Salesforce Id that got allocated (because you might well need that for a child object you're going to import next, etc. You cant always use externalids in all situations to relate objects)
b) for your failed rows (and in real life there are always failed rows) you want to know what the errors are - locking, invalid picklists, valdiation rules etc
So a new command something like ...
sfdx force:data:bulk:results --jobid 750xx000000005sAAA
... which then gives you all the results files (from each batch) concatenated together into one big CSV would be REALLY useful
Many thanks
Beta Was this translation helpful? Give feedback.
All reactions