So i originally built my app using Google sheets due to my partner wanting easier access to data at the time. Now, I’m attempting to move everything into Glide native tables. I added some user-specific columns here and when looking into solutions of how to move them, I’m thinking the only way is to have the user do it via a workflow where I ask them to migrate their data to another table. I can see that this will probably end up in a large update count on my end, but is this the best course of action?
The only other method I thought of was to leave the user specific columns and just tie them via a relation, but honestly, I’d like to just remove the google sheet integration for any performance gains. Unless there aren’t any haha.
Any help/advice/suggestions would be greatly appreciated. I have about 400 users using the app if that is a factor as well.
If you want to migrate to Glide table, you should do it all the way or not at all. Else, you will complicate yourself so much by duplicating all your screens to work with both google Sheets and new Glide tables. Not even talking about alll the conditions that you would need and all the duplicated computed columns and workflows…
yeah, i’m pretty much at 30 or so glide tables but have two of them left (holds my primary data and also tied to google sheets) that have a ton of computed columns and user specific columns. So my dilemma has been do I just leave them and keep building more things or should I begin to find a way to migrate from them which does mean I’m almost rebuilding a good chunk of my app.
If your plans are to remove Google Sheets at the end, yes, I would find a way to migrate before building more features. Because later, you will have more things to migrate.
that’s what I was afraid of haha. I think the concern for me is whether google sheets creates a constraint for me later or if it prevents me of utilizing a future capability. Also, I assume for the user specific columns, I’d have to have users “migrate” data through something like a workflow? From what I can tell, there’s no way to migrate that data otherwise.
Yeah, this is probably your best bet. The only problem is relying on multiple users to run through their data timely to minimize downtime. One thing you may want to consider is doing it yourself by previewing as each individual user. You could probably create a screen with a collection that has a workflow to migrate the data. You could rapid click though each row. You could also add a filter to the collection to only show rows that haven’t been migrated yet, so you know when you are done. A bit of manual work, but so is rebuilding parts of your app.
Or, he could migrate every column except user-specific ones, and let the user migrate the user specific ones? Might be complicated, but surely less complicated then viewing each 400 users view to copy paste data…
at least the thing i’ve taken from this is no one said, just stay on google sheets bc it’s less work. So that at least tells me it’s probably worth it at some point to get off that integration
Anything new I create is purely glide tables. However my primary app is mostly google sheets. Partly because it was built when google sheets were the only option, and partly because I have back end scripts that archive and backup data. Eventually I’d like to migrate more of the tables away from google sheets, but not sure if I’ll ever go all the way.
I think the overall experience is going to be better with glide tables because there is less overhead with the extra syncs and updates incured with those syncs.
The only reason why I would use google sheet, is of I need automatic Template as basic column or multiple roles with the (Role 1, Role 2, Role N) technic.
