Check whether the outcome improved
Exercise preview actions without execution
Upload the fixture, inspect validation, change mappings, refresh, and revisit preview through supported navigation. Compare destination records after each action. Record expected preview bookkeeping separately so the check can identify a real domain write without incorrectly requiring the entire system to remain unchanged while an uploaded file is prepared for review.
Check leaving and repeating preview
Leave the flow through its supported cancel or back action and reopen or repeat preview. Confirm destination state still matches the baseline and the interface accurately describes what was retained. Do not assume that cancellation repairs a write; verify the absence of premature destination changes before depending on any later recovery behavior.
Confirm the explicit execution boundary
Review the final inputs and execute the import through the documented action. Compare intended destination changes with the fixture and check the resulting status. Confirm validation remains useful before execution and that a repeated preview request cannot be confused with the operation that is supposed to commit the reviewed work.
What to carry forward
Accept when preview actions preserve destination state as promised and explicit execution performs the reviewed import. Record any side-effect boundary not observed separately. A passing request response or unchanged visible list is insufficient if the relevant destination records and their field values were not compared with the controlled baseline.
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