Aglet

Verify Import Mapping and Field Integrity

Mapping verification checks field identity, value fidelity, type handling, defaults, and rejection outcomes together. Run a fixed import fixture with distinct column values and a bounded representative file. Compare stored destination fields and error classifications, not only accepted row totals.

Check whether the outcome improved

  1. Assert column identity

    Use fixtures where every source column contains a unique recognizable value, including similarly named fields and reordered headers. Assert each destination field receives the intended value. Include an omitted optional column and duplicate or unknown header to verify visible handling.

  2. Check value fidelity

    Test empty, zero, formatted, boundary, unicode, numeric, and date-like values according to the destination contract. Compare parsed, stored, and displayed representations. Confirm defaults apply only to documented cases and that valid source values are never replaced silently.

  3. Verify revision boundaries

    Run affected and current header versions through the intended mapping selection. Compare accepted rows, rejected rows, destination fields, and import diagnostics. Retain fixtures and outputs with the mapping revision, and document source formats or historical runs that were not covered.

What to carry forward

Accept the mapping when distinct source columns reach the correct destinations, valid values retain their meaning, unsafe inputs have explicit outcomes, defaults follow the contract, and revisions select predictably. Keep verification open for undocumented headers or unreviewed historical cohorts. Report every fixture and source limit.

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