If I wanted to move a subset of my users into their own seperate table, so I do a query to get that subset then export a csv, firstly would that work to then import that csv into a new table? And secondly if there’s 18 columns that I’ve exported but I only need their name, address and number, can I only make those 3 columns then import? Or will I need to make all 18 for the importing to be successful and then delete from there?
May I ask why you do this instead of using a column to filter them?
Row limit and they have no need to be in Users table in the first place they have no interaction with the app, all I need to pull is their photo + phone no. Hence why I’m curious about how CSV importing works exactly in regards to columns
I’m not sure, but I would have to think that the columns have to match between the export and the import. I think it would be pretty easy to just test it out and see what works and what doesn’t work.
3 Likes
Please be careful since if you still use those rows somewhere in the app, it would still count against your quota.
Regarding the import part, if you create a new table with just 3 columns, I believe the import file only needs to have 3 columns, otherwise Glide might try to add columns that don’t exist yet. Make sure the names match.