Import records and perform reviewed bulk updates

Prepare reusable data files and change selected records while preserving identifiers and the intended scope.

Before you start

Have permission on the target model, a reviewed file and the list of records to change. Test the intended mapping on a small controlled sample before a full import.

Step by step

1. Prepare identifiers and relations

From the target list, export the required fields using an import-compatible export when records will be updated. Preserve External ID to identify existing records, and review company, dates, decimal format and related-record identifiers. Keep the original export for comparison.

2. Test and import

Choose Import records, upload the file and review every mapped column. Use Test to identify missing relations or invalid values, correct the file and repeat until resolved. Import the reviewed file, then inspect record count and representative totals. Accounting journal imports additionally require the configured journal, file layout and completion rules.

3. Apply a configured mass edit

Filter the intended records, explicitly select them and open the configured action under Action. For each field, choose Set or Remove only as intended and inspect the proposed values before applying. Verify a sample afterward. Creating a mass-edit action and its allowed fields/groups belongs to the administrator.

4. Review automation effects

Check whether saving or importing triggers configured automated actions, messages or computed values. For a new automation, have the administrator review trigger, record filter, action and a controlled example before enabling it for the full record set. Retain the file and result of the update.

Expected result

Records were updated with stable identifiers and a reviewable before/after comparison.

If something goes wrong

Repeated imports without identifiers can create duplicates. A successful Test validates the file, not every downstream business effect. If an update affects unexpected records, stop further batches and compare the saved export before attempting a correction.

Continue the process