Aglet

Triage an Import Mapping Data Quality Issue

Import mapping defects can swap fields, drop columns, coerce values, or apply a default that looks valid. Triage should capture the source header, destination contract, mapping revision, and representative accepted and rejected rows. Bound the affected import runs before proposing a corrected mapping.

Establish what is happening

  1. Inventory source and target

    List incoming columns, destination fields, expected types, requiredness, transformations, defaults, and ignored attributes. Mark fields with similar names or units. Preserve the exact header order and a small row sample so positional or name-based mapping behavior can be compared.

  2. Compare mapped values

    Trace representative values from source cell through parsing, normalization, mapping, validation, persistence, and display. Classify swapped, missing, coerced, defaulted, rejected, and correctly imported fields. Include rows with empty, zero, formatted, and boundary values.

  3. Bound affected imports

    Group discrepancies by import run, source format, mapping revision, column, destination field, and date. Compare accepted and rejected row counts with expected totals. Identify whether the issue begins at one header version or appears across historical runs.

What to carry forward

Deliver an import scope brief with source and destination contracts, representative mappings, affected runs, discrepancy classes, and the earliest mapping boundary. Triage stops when the mismatch is reproducible from recorded input. Keep repair undecided for ambiguous columns or values whose intended meaning is not documented.

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