Understanding Field Mapping

Zuora Data Loader performs field mapping by matching the fields in the target Zuora object with the column headers in the source CSV file. Data Loader attempts to automatically match field names in Zuora with the column headers in the CSV file based on exact or similar names. For example, if Account Name is the target field and the CSV has a column named Account Name, the tool maps them. 

The following are some key points to remember while using Zuora field mapping: 

• If automatic mapping does not identify all fields, the user can manually map the CSV columns by clicking on the dropdown.
• If any required field is unmapped, a warning message is displayed to guide the user, as unmapped required fields can cause errors.
• Data Loader allows users to save field mappings for future uploads. However, if the source CSV file or target fields change, such as by adding a new custom field, the user will need to update the mappings to include the new field.
• Data Loader supports one-to-one field mapping only. Attempting to map a single source field to multiple target fields will result in errors. In such cases, a warning message is displayed to help resolve the mismatch.
• If a non-mandatory field needs to be modified, ensure the field is included in the CSV template and properly mapped in the field mapping interface between the target and source columns. For example, consider a custom field like CollectionAgent_c on the Product Rate Plan Charge object. Although this field is not mandatory, if records need to be updated for this field, it must be present in the CSV and correctly mapped in the field mapping interface. Proper mapping is essential for the successful creation and update of records.