Check whether the outcome improved
Check each supported source layout
Exercise files with and without headers, plus documented introductory-line handling. Include all-text records and a first value resembling a field name. Confirm the expected labels and exact first data record, rather than accepting whatever labels the detector produces as the definition of success.
Exercise the confirmed override
Where a header setting exists, change it in preview and return to the correct choice. Continue through import using the same file. Verify the selected row offset persists and the importer does not redetect the layout differently after users already approved the preview and field mapping.
Compare complete row identity
Inspect the saved first and last records and reconcile the full controlled row set. Try an invalid introductory layout and review the correction message. A useful failure should explain the unsupported structure without silently discarding a line merely to make the remaining file parse successfully.
What to carry forward
Accept when labels, row offsets, and stored records agree for every supported layout exercised. Record unsupported introductory formats explicitly. If execution or exact record comparison was skipped, keep that limit visible; a preview pass alone cannot prove the first data row survives the final import.
Technical background: PostgreSQL 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