# Glide Tables

**URL:** <https://community.glideapps.com/t/glide-tables/67304>\
**Category:** Ask for Help\
**Created:** [October 26, 2023, 10:45am UTC](https://community.glideapps.com/t/glide-tables/67304 "2023-10-26T10:45:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohnB](https://avatars.discourse-cdn.com/v4/letter/j/4491bb/32.png) [@JohnB](https://community.glideapps.com/u/JohnB)\
**Post date:** [October 26, 2023, 10:45am UTC](https://community.glideapps.com/t/glide-tables/67304/1 "2023-10-26T10:45:31Z")

</div>

Hello Glide gurus, would anyone be able to assist with the following pls?  
In prep for switching to Glide tables and before I make the leap, any comments on the following apparent disadvantages, and how I can overcome?

1. Data backups. Are there 2 options I can see (A) Go to “settings”, then “export app data” or (B) simply save the current app and create another version, thereby “saving” the data. Which is preferred?
2. Loading data back into Glide.  
(A) I understand this has to be done table by table? Is this correct? (If so, this kills it for me).  
(B) What if I import a new table, and there are discrepancies, as follows:  
(i) different number of rows. What is actually uploaded?  
(ii) discrepancy between the data item column-names in the current table and the table being uploaded. Does Glide refuse to import or does it import and tell you which columns it’s not loaded
3. Can you import a single column of data into Glide.
4. Is the cut and paste function into Glide reliable (eg during internet signal drop-outs & when Glide sometimes has to reload)
5. Anything else I need to consider  
Thx in anticipation of your knowledge and expertise !

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [October 27, 2023, 12:44am UTC](https://community.glideapps.com/t/glide-tables/67304/2 "2023-10-27T00:44:00Z")

</div>

> [@JohnB](#):
>
> Data backups. Are there 2 options I can see (A) Go to “settings”, then “export app data” or (B) simply save the current app and create another version, thereby “saving” the data. Which is preferred?

I think both works, if you care solely about the data. Duplicating the app would mean you also have a copy of the layout at that point in time. We do this for a few cases at our agency, in case the client changes and breaks something later down the line, we can have a reference of what it was before.

> [@JohnB](#):
>
> I understand this has to be done table by table? Is this correct? (If so, this kills it for me).

Uploading an Excel file will mean Glide creating all tables automatically for you.

> [@JohnB](#):
>
> different number of rows. What is actually uploaded?

They append the rows, it’s not an overwrite on the old data. Say you have 5 rows, then your data have 5 rows, it will be added as 5 new rows so you get 10 at the end.

> [@JohnB](#):
>
> discrepancy between the data item column-names in the current table and the table being uploaded. Does Glide refuse to import or does it import and tell you which columns it’s not loaded

I believe new columns name will be created, and the values will be loaded to new rows, related to the “not overwriting” point above.

> [@JohnB](#):
>
> Can you import a single column of data into Glide.

If you mean adding a single column into an existing table, I believe you can just copy paste it. There’s an outstanding bug regarding encoding in the data editor, so copy pasting might not be reliable until that is fixed.

> [@JohnB](#):
>
> Is the cut and paste function into Glide reliable (eg during internet signal drop-outs & when Glide sometimes has to reload)

Most of the time it should be reliable, I think they give you a load indicator at the bottom of the screen so you know the new values have been saved or not. Don’t try it with too much data though.

---

<div class="post-metadata">

**Author:** ![JohnB](https://avatars.discourse-cdn.com/v4/letter/j/4491bb/32.png) [@JohnB](https://community.glideapps.com/u/JohnB)\
**Post date:** [October 28, 2023, 8:20pm UTC](https://community.glideapps.com/t/glide-tables/67304/3 "2023-10-28T20:20:35Z")

</div>

Thanks! Sounds like using Glide tables runs a higher risk of introducing accidental errors, I’ll give it a wide berth.

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [October 29, 2023, 2:32am UTC](https://community.glideapps.com/t/glide-tables/67304/4 "2023-10-29T02:32:41Z")

</div>

It’s just a temporary bug that Glide is working on for a fix. Most of the time I would suggest using Glide Tables.

---

<div class="post-metadata">

**Author:** ![JohnB](https://avatars.discourse-cdn.com/v4/letter/j/4491bb/32.png) [@JohnB](https://community.glideapps.com/u/JohnB)\
**Post date:** [October 29, 2023, 4:38pm UTC](https://community.glideapps.com/t/glide-tables/67304/5 "2023-10-29T16:38:51Z")

</div>

My app is data heavy and quality is essential, so can’t possibly risk anything that’s not 100% reliable. Thx for the clarification.
