Decide where the work belongs
Identify unconfirmed destination changes
Compare controlled destination state before and after preview without confirming execution. Record created or updated records and their affected fields. Distinguish an unintended domain write from metadata needed to show the preview, while preserving evidence if a validation-only action invokes work that the user was told would happen later.
Scope the triggering preview path
Compare upload, validation, mapping changes, back navigation, and refresh through supported paths. Identify which action first causes the destination change and whether the effect repeats. Estimate reach from those interactions rather than every import, keeping unrelated background edits outside the scope unless source identities connect them to the preview.
Assess visibility and reconciliation
Check whether the interface reveals the early change and whether users can identify affected records. Determine what evidence supports reconciliation without guessing prior values. A confirmation dialog added after the write does not restore review control, so include the need to correct the execution boundary in the priority assessment.
What to carry forward
Record priority with confirmed premature changes, triggering paths, visibility, and recovery effort. Assign an escalation trigger for repeated preview writes or updates to existing records. Keep the decision focused on preserving the stated review boundary, with expected bookkeeping explicitly excluded from the claim of an unintended import.
Technical background: Django import-export documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow