Performance Considerations During Record Updates

To update sublist data in existing records, instead of using a single import file that includes body field and sublist data, consider using a separate import file for the sublist data, in which you provide a reference to the record you want to update. This approach leads to improved performance.

Important:

If you move a set of sublist data to a separate import file, you must do this with all other sublist data. In the following example, if you move Item and Quantity into a separate Item import file, you must also move Apply and Payment into a separate Apply import file.

External ID

Customer

Item

Quantity

Apply

Payment

CM-PT3–042601

ABC Trucking

Carburetor MK60

10

EXTINV02134

2500

CM-PT3–042601

Carburetor MK65

3

EXTINV02183

1500

CM-PT3–042601

EXTINV02190

750

CM-PT3–042602

Happy Day Motors

EXTSO12456

500

CM-PT3–042603

Smithson Auto Body

Alternator BS40

2

EXTINV02210

1200

CM-PT3–042603

Alternator BS52

3

EXTINV02199

300

When you move sublist data to separate import files, make sure that the primary import file only contains data for body fields. If the import has more than one import file specified, multiline sublists are not supported. In this case, you must add all sublist data into separate import files, refer to the record ID in each additional file, and run the import.

Related Topics

Importing Sublist Data in a Single File
Import Format and Mapping Considerations
Import File Examples
Limits of Using Multi-threaded CSV Import

General Notices