Describe the problem you are trying to solve
The Load Records to Multiple Objects feature requires every column header in the uploaded workbook to exactly match a Salesforce field API name. If a header doesn't match, the column is reported as "does not exist on the object" and is dropped from the load, so the user has to go back to their spreadsheet, rename the headers, and re-upload.
Files that come out of other systems (or that a business user maintains) almost never use API names, so this is a real barrier compared to the single object Load Records flow, which already has a full field mapping step — auto-mapping by label/API name, manual overrides, static values, related-record lookups by external Id, and saved mappings that can be re-applied to future loads.
Describe the solution you'd like
Add a field mapping step to the multiple objects load, ideally reusing the mapping UI from single object load:
- For each worksheet, list the file columns and let the user choose the target field on that worksheet's object, with the same auto-mapping by API name / label as single object load
- Allow a column to be explicitly ignored instead of silently dropped
- Keep the structural columns working as they do today — the
Reference Id column and {curly brace} relationship columns are not field mappings and should be recognized and displayed as such rather than requiring the user to map them
- Report mapping problems (unmapped column, unmapped required field) in the existing error summary on the review screen
- Support saved mappings per object so a recurring load of the same file shape doesn't have to be re-mapped every time
Related but distinct: #646 (mapping a single file column to multiple Salesforce fields).
Describe the problem you are trying to solve
The Load Records to Multiple Objects feature requires every column header in the uploaded workbook to exactly match a Salesforce field API name. If a header doesn't match, the column is reported as "does not exist on the object" and is dropped from the load, so the user has to go back to their spreadsheet, rename the headers, and re-upload.
Files that come out of other systems (or that a business user maintains) almost never use API names, so this is a real barrier compared to the single object Load Records flow, which already has a full field mapping step — auto-mapping by label/API name, manual overrides, static values, related-record lookups by external Id, and saved mappings that can be re-applied to future loads.
Describe the solution you'd like
Add a field mapping step to the multiple objects load, ideally reusing the mapping UI from single object load:
Reference Idcolumn and{curly brace}relationship columns are not field mappings and should be recognized and displayed as such rather than requiring the user to map themRelated but distinct: #646 (mapping a single file column to multiple Salesforce fields).