Skip to content

CSV Import Thoughts #2800

@squigglybob

Description

@squigglybob

Feature requests

  • When importing a large number of records, it would be good to have any errors show up in an error console during the import.
  • It would be good to have a stop import button.
  • A 'title' field is required for the importing to work. Rather than require the incoming CSV to be updated to create the title field, we could require that one of the fields be marked as 'to be used for the title' as well.

These 2 features would make the iteration loop quicker to get clean import of data.
E.g. Importing 2000 records with nearly 70 fields took a long time, but none of the records imported due to errors on every record.

Bugs

  • 0 is not recognised as a value in incoming CSV
  • 0 is not recognised by DT in record editing
  • When in region of 50 fields and some very large key selects with thousands of options, the page slows down, and the auto-map for key selects doesn't seem to do anything.

Speedup

  • Is there a way to make importing more efficient so e.g. the above scenario would import quicker? 50 fields and 2000 records, takes over an hour to import

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions