# Salesforce Bulk API 2.0 synthetic examples

All records are invented. These files exercise documented CSV shapes, not responses captured from a Salesforce org. Error wording is illustrative; configured fields External_Id__c and Parent.External_Id__c are assumptions. Do not submit these files to production. IDs are demonstration strings, not verified destination IDs.

Select COMMA and the roles in the filenames. Original and unprocessed cannot be detected from headers: choose the role explicitly. Use External_Id__c for exact, case-sensitive source matching.

A: 3 failures (required field, restricted picklist, locking). Industry is mentioned but absent from the supplied schema, so it is not asserted as a known field.
B: load B-successful and B-failed together: 1 successful, 1 failed; no unprocessed evidence.
C: load original and failed together: 4 failures, one repeated key DUP in each population, one empty key, one unique local key DEST-DUP whose error describes multiple destination matches. Missing local keys are warnings, not invented Salesforce error codes. The row with no key also lacks Name; its required-field result is independent of the local missing-key warning.
D: complete demonstration: 5 original, 3 failed, 1 successful, 1 unprocessed. The failed results are deliberately reordered. All 5 results match uniquely by External_Id__c. The counts describe supplied evidence, not independently verified job totals.
E: source order 001,002,003 versus results 003,001,002. All three match exactly by key. Positional matching would corrupt the investigation.
F: change only Name for key 001 from empty to Alder Books. Select the row for retry, mark it reviewed, select failed, upsert, External_Id__c and confirm destination review. The exported CSV must match F-reviewed-retry.csv exactly. This is a candidate, not an accepted Salesforce upload.
G: 2 failures; one validation error and one deliberately unclassified illustrative code. Preserve quoted commas, doubled quotes, embedded LF, Unicode, empty strings, leading zeros and long numeric strings. The formula-looking Name must remain literal text in the tool; never open raw retry files as trusted spreadsheets.

Worked D investigation: obtain the name for 001 from the source owner; look up the actual parent for 002 before replacing P-MISSING; resolve multiple destination matches for 003 inside Salesforce. Do not guess parent keys or remove duplicate destination accounts automatically. 004 already succeeded and must never be retried. 005 was unprocessed; inspect current state and stale values before including it.

example-findings.csv is generated from the D result files with the same engine as the tool. retry-checklist.html is printable from your browser. complete-dataset.zip contains all CSVs, this README and the checklist. Automated tests check every CSV and the reordered matching and exact F correction.