Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
Bulk API is based on REST principles and is optimized for loading or deleting large sets of data. You can use it to query, insert, update, upsert, or delete a large number of records asynchronously by submitting batches which are processed in the background by Salesforce.
1
vote
Accepted
Transformation Spec limitation in Bulk API v1.0
Likewise we ran into this too - verified with tests.
Can we work around this?
Our workaround is to rename all the headers in our file to the corresponding Salesforce field name and bypass the t …
1
vote
0
answers
533
views
Bulk Job Status - Failed vs Not Processed?
What are the use cases for setting a Bulk (version 1) job to a status of Failed vs Not Processed?
Salesforce documentation gives the same description for both
The batch failed to process the full …
1
vote
1
answer
814
views
Bulk API V1 Query - ResultId missing when running concurrent Bulk Jobs
When querying for the result ids of a batch on a closed Bulk (v1) query job, sometimes the result id is not returned; instead the full returned xml is:
<result-list xmlns="http://www.force.com/2009/0 …
0
votes
Accepted
Bulk API V1 Query - ResultId missing when running concurrent Bulk Jobs
Result was a bug in the custom code that prematurely determined results were ready to retrieve from the bulk query job. My criteria was checking job completion instead of batch completion.
What is …