Problem Definition

When Importing CSVs/External Import to Assets for JSM, the Log does not convey errors to the User clearly. One of the following scenarios tends to occur:

1. No error is provided, such as with an Invalid File, where Dev Tools are needed to see the error.
   
2. Errors are provided, but they are cryptic, such as when there are Constraint Violations on Attributes attempting to be imported.
   
3. Objects are not created but it is not treated as an error and no information is provided as to why the Objects aren't created.
   
   This image of an Import's statistics is for an Import that was treated as a "Success". But it does not convey why only 2 of 3 objects were created.
4. Objects are not created because not every entry in the CSV file is parsed; the import log doesn't show why it stopped processing the file.
   
   This image of an Import's statistics is for an Import that was treated as a "Success". But it does not convey why only 108 objects were created if the file had 767 lines. (The backend shows this was due an extra double-quotes (") causing the EOF error.)

Suggested Solution

Provide a clear log for each import. Enable exporting this log to see detailed object-by-object processing and how the Importer chose to handle the object.
Include line of import that lead to the error.

Workaround

There is no current workaround. One will be added to this request should it become available.