CSV import in the Trade History tab currently fails silently if columns are missing or malformed, and does not provide users with detailed error feedback. Trades with missing or incorrectly mapped fields may be skipped, and users are only notified of the total rows imported. There is also no preview of how CSVs will be mapped before import.
Recommendations:
- Show users a preview of CSV file mapping before import, including which fields will be mapped and any missing/extra columns.
- If any rows fail to import (e.g. due to missing required fields or parsing errors), display a detailed error message indicating which rows failed and why.
- Improve validation during import to ensure all required trade fields (id, symbol, entryPrice, etc.) are present and correct.
- Summarize results for the user, including number of trades imported, number skipped, and specific errors.
This will improve usability and reduce silent data loss for users importing trades.
CSV import in the Trade History tab currently fails silently if columns are missing or malformed, and does not provide users with detailed error feedback. Trades with missing or incorrectly mapped fields may be skipped, and users are only notified of the total rows imported. There is also no preview of how CSVs will be mapped before import.
Recommendations:
This will improve usability and reduce silent data loss for users importing trades.