This request is for the JCMA/CCMA migration tools to improve the details of the error when importing the users' assessment CSV file. Currently, we only have two generic errors from the CSV import process:

1.  Invalid CSV file
   1. This error indicates a syntax error in the values of the fields Tombstone, ErrorType, or AccountType. Also can be related to the quantity or position of the comma delimiter or any unexpected character in the CSV file.
2. Users don't match
   1. Indicates that an inexistent user was added to the column UserKey. 

Troubleshooting issues in a CSV file is painful and can take days to find the specific line with the error. Most customers have thousands of users/lines in the CSV file, and if they input any unexpected character or create a malformed CSV file, it is really tough to find and fix the errors.

Please improve the error message from the JCMA/CCMA users' assessment by using a CSV import file to show the line number and root cause of the error, so the customer can easily fix the issue in the CSV file.