The current error messages from the data importer lack details, leaving users without a clear understanding of why an import fails, such as with Excel imports. Although printing the stack trace which includes details is possible, it is not user-friendly.
A better approach would involve adding a detailed error message that includes:
This would help users easily identify and correct any incorrect datasets.
Current error message example: "Incompatible data conversion"
Suggested improvement: "Unable to parse a source value in row 4: 'a' into a Boolean"
Hi @ErkangHui,
you can use the error message that is logged or you can make use of Error Handling and print out a message containing the details.
Hi, sir, how to use stack trace to see the detail error information?