Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Decision and scope
Separate file reading, validation, preview and application. Define stable keys, mandatory fields, accepted formats and the duplicate policy before importing real records. The preview should explain how many records will be created, updated or rejected and which existing records are affected by an update.
Illustrative example
Illustrative example: a file contains one hundred customers, three repeated identifiers and two incomplete email addresses. The preview identifies the exact rows and reasons. The user can correct the file or explicitly exclude invalid rows according to the agreed policy. Submitting the same file again must not create another copy of every customer.
Acceptance check
Test separators, leading zeroes, dates and partially valid files. Preserve a result report and import identifier. Accept the workflow when users can inspect the impact before changes are applied and every error points to a concrete correction.
Key takeaways
- Accept the workflow when users can inspect the impact before changes are applied and every error points to a concrete correction.