Import error log enhancement in new UX


Suggest to enhance the current import error report in the new UX. The new overview only contains very limited information about any errors which occurred during import and it is not possible to get a preview of the errors as you can in the classic UX. At the same time, the ability to export errors is limited to 50,000 rows and for the full process chain. I.e. if a process consists of multiple actions it would not be possible to see or download the full error log for the process - only for the first action(s) until the row limit has been reached. Some improvements which would help transition from the classic to the new UX:

  • Ability to see preview of individual process step errors after import (as in classic UX)
  • Ability to export individual process step errors (as in classic UX)
  • Show least occurring errors first (would ensure the 50,000 row limit would not be an issue)
  • Ability to hide selected types of "errors" (e.g. the "Another row has already been processed with this key" error is not really an error and confuses the end user)
24 votes

On Roadmap · Last Updated


  • Status changed to: On Roadmap
  • Really support this. It would be ideal to have the users be able to see the error log as you can when are importing into a model through the back end. I.e. for every error, have a log that shows the row, and the reason why the error has occurred. This could further be enhanced to also tell you what rows have been ignored and for what reason. Our users primary use uploads due to the amount of data that needs to be input to our models, therefore, it would be really beneficial to know what has not been uploaded on the UX pages.

Get Started with Idea Exchange

See our Submission Guidelines and Idea Evaluation Criteria, then start posting your own ideas and showing support for others!