We have the same issue and have to analyse the file manually

We enter a lot of our data manually in our current solution. We won't be expanding to other use cases until this is available. It is too much work to have to manually compare the data in Caspio to the data in the sources (which are updated on at least a daily basis).

Another year, another vote for this being needed. This is pretty basic! I'm currently trying to import an xlsx file into a table and every single record is erroring. What does the message tell me about error conditions? NOTHING. It obviously knows what the issues are or it wouldn't have failed to import the records. Why can't that information be provided?

This would be great!

Yes, this would be great if the error detail would say which row had the error. Sometimes I import a file with 9000 records and I might have one record fail and then I have to figure it out. This would save me hours in work because on some of my imports, I have to enter certain information in the file first before i know if there was an error I wouldnt know which row so I put a unique value manually on everything so I dont get any errors. Very time consuming

It would be very useful to see failed records

Much of our data is imported into the database with a CSV file. Some files can have 9000 rows.
It is very important for me and I am sure for others to have more details given about an error during import. Even a debug page that someone could look at and decipher what went wrong.

This is a great suggestion that just celebrated it's 3rd anniversay. What a concept (in the year 2018) that an import function should tell you which rows failed to import instead of just how many failed to import. I add to the suggestion that the import should report which row(s) failed, which field(s) within the row(s) failed, as well as the reasons for the failure(s).

Same need for us