Aglet

Verify Import Errors Point to the Correct Source

Verification should demonstrate that a user can find and correct the rejected source value from the reported error. Use independently recorded coordinates and follow the real correction path. A technically accurate validation rule is not enough when the displayed row, column, or mapping label points to a different place in the file.

Check whether the outcome improved

  1. Check representative source coordinates

    Exercise one invalid value after headers, skipped lines, and multiline records where supported. Compare the reported location with logical record and physical line references. Confirm the numbering convention is understandable, including whether a header counts, rather than accepting a consistent offset as harmless because an engineer can explain it.

  2. Check column and mapping context

    Map source labels to different destination names and inspect the error’s field reference. Include repeated source headings if supported. Confirm the message or report provides enough context to identify the actual source column without guessing which equally named heading or unfamiliar destination attribute contains the rejected value.

  3. Complete the correction journey

    Follow the displayed location, correct only the intended invalid value, and retry through the supported flow. Include several rejected records to check stable references across the report. Compare the remaining valid source values and final import outcome so the correction does not accidentally modify an unrelated record directed by a stale error position.

What to carry forward

Accept when reported references lead to the correct source values and the correction journey succeeds for the supported layout matrix. Record unavailable report formats separately. A parser-level coordinate pass remains incomplete if the rendered message, downloadable report, or actual retry path was not exercised with those same references.

Technical background: DuckDB 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