Skip to content

🔦 Feature: Have an external log for viewing the import errors #6529

@tjoneslo

Description

@tjoneslo

Please confirm if feature request does NOT exists already ?

  • I confirm there is no existing issue for this

Describe the usecase for the feature

I have tried several times to import data into my Nocodb both via the air table import and the CSV import. All of these attempts failed, usually because the data conversion wasn't correct. The problem is the error message generated:

  1. Is put onto a pop-up dialog that has no ability to allow cut/paste of the error message. This makes reporting the error hard because I now need to type the error message into any bug report. This is error prone.
  2. Once I close the modal dialog box, there is no way to look at the error message again. I must delete the tables and re-import the schema and data to see the message again.
  3. In some cases the import error exceeds the size of the dialog box with no way to scroll to see the whole message.

I understand doing data conversion this way is hard, but if I can't see the error messages and be able to correct the data for the limited ability of nocodb to do data scrubbing. I will never get my data into this tool.

Suggested Solution

  1. Better error messages for import to highlight the failures
  2. Keep the import logs with the base and allow viewing.

Additional Context

An example of the overisized error message.
image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    ✅ Closed

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions