“Add import” is not a complete requirement. Users need to know which columns are accepted, which values are valid, what is mandatory, and what happens when one row fails.
A reliable import workflow starts by downloading a template, validates before writing, reports errors by row, and makes retries safe. Export should preserve enough structure to be useful without leaking fields the user is not authorized to see.
The template is not documentation stored somewhere else. It is part of the user experience and part of the contract between the application and its data.
A good test includes an empty file, a duplicate, an invalid reference, a partial failure, and a file produced by the export itself.
Top comments (0)