Data Import - Suggestions #649
Replies: 2 comments 1 reply
-
I agree and think we should keep things simple for now. CSV import on the creation of a new table suffices. What other considerations should we make for data importing into budibase? What makes a great data import experience into no-code tools? In which cases is CSV import not enough? |
Beta Was this translation helpful? Give feedback.
-
If we support an initial bulk import, I think that we should also support a bulk delete. Often people will "Have a go". They will realise a mistake, and try again. So - i agree that starting with "Create Table from CSV" only makes sense, as they can just delete the table. |
Beta Was this translation helpful? Give feedback.
-
Importing data into budibase is a key element that has been asked for by quite a few customers.
The question now is how data should be imported into budibase applications.
At a high level, data import makes sense in these cases:
Creating a new table from already existing data
In this scenario, we would need to determine the schema by reading the headers of the CSV and make them all strings. I don't feel like it's worth trying to be more sophisticated than this.
Adding "more" data to an existing table
In this scenario, we first need to check that the headers match the existing table headers. This could be tricky, given that the existing table headers may not be strings. I suggest we do not implement this and only allow people to create new tables from data imports.
UX
On creation of a new table in the builder, you see this UI:
Adding a "Import from CSV" button here seems like a reasonable solution. Once you click that you can then select a CSV from your machine and use it to create a new table after we have validated it.
Beta Was this translation helpful? Give feedback.
All reactions