Establish what is happening
Bind preview to its source
Record the controlled file identity, preview timestamp, mapping selections, and relevant parser options. Compare these with the final import’s recorded inputs. Keep a stable file fingerprint or equivalent revision reference when available; the same filename can refer to different uploaded contents at different points in the flow.
Identify the first changed input
Compare selected source columns, destination fields, format choices, and execution revision. Find the earliest difference rather than treating all final-value discrepancies as parsing errors. Check whether navigation, file replacement, or a second editing session changed state after the preview was shown but before confirmation completed.
Trace one unexpected field
Choose a distinct fixture value and follow its approved mapping to the saved destination. Determine whether the value changed or the target changed. If recorded execution inputs match the approved preview, keep a parser or assignment defect in scope rather than assuming the handoff itself is responsible.
What to carry forward
End with the approved preview inputs, executed inputs, first mismatch, and one traced outcome. State which revision evidence is missing. The next owner should be able to distinguish a stale preview, changed settings, and an execution defect without reconstructing the entire workflow from memory.
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