Customer CSV mapping screens, not a Retick importer
Review column mapping before similar headers point to different fields
Use synthetic headers and sample cells to inspect how your importer explains each source-to-destination assignment.
- ✓Different headers truncate identically
- ✓Duplicate destinations are hard to locate
- ✓Returning silently resets mappings
Evidence for clearer source-to-field choices
Source identity preserved
Show the full distinction between similar headers before evaluating the selected destination.
Mapping evidence checked
Correct candidate findings that confuse a source column with an application field.
Back navigation reviewed
Define what should happen to assignments when an operator revisits file selection.
Review the source-to-destination decision
An operator imports a synthetic contacts sheet into your application. Two source headers begin with Contact, and the mapping view truncates both to the same text. The operator cannot tell which column supplies the display name. Retick reviews captures of your CSV importer; it does not provide a general CSV ingestion or mapping service. Keep the review focused on the choices your interface presents.
Build a harmless mapping fixture
Use an approved sample CSV containing fictitious names, reserved example addresses, and visibly different headers such as Contact display name and Contact department. Capture the mapping view, opening a destination selector, changing a mapping, and moving back to file selection. Note build, viewport, fixture encoding, delimiter, and intended field assignments. Upload authorized media or record with the supported browser extension, keeping local paths and real datasets out of view.
Preserve the mapping relationship
A concrete issue is Truncated source headers conceal which contact column is mapped. Annotate the competing labels and sample row values. Review Retick's AI candidate findings, editing any draft that reverses source and destination. Reject claims that records were imported incorrectly when the capture ends at mapping. A label ambiguity, a duplicate destination assignment, and lost mappings after back navigation need separate findings and separate expected results.
Example acceptance criteria
The mapping interface should let the operator distinguish the complete synthetic source headers using the approved presentation. Each destination selection should remain visibly associated with its source column and sample value. If duplicate assignments are disallowed, the agreed warning should identify both affected choices before continuing. Returning from the previous step should preserve or reset mappings according to the product's stated rule. Verify those branches manually with the safe fixture.
Recheck headers beyond the happy path
Keep initial, edited, and returned mapping states in a review cycle. Follow up with an unmapped optional column, an empty sample cell, reordered headers, and a longer destination label. Download reviewed findings or create selected individual-media Trello cards. Retick does not parse the CSV for your application, execute the import, or validate stored field values. Parser behavior, data transformation, and persistence require separate application tests; clear mapping labels alone cannot establish correct imported records.
Make each column assignment distinguishable
Review a harmless CSV fixture and capture the mapping decisions before import.