EXCEL/GLIDE Synchronization

[Javier_SBT]

Good morning again.

A situation is happening to us that has us intrigued…

We are making a preliminary prototype and with a set of tests in a table in Excel and therefore in GLIDE.

It is happening to us that “sometimes they appear” in GLIDE, let’s say 500 row records, and “sometimes they appear in GLIDE,” let’s say 300 row records… IN EXCEL THERE ARE ALWAYS THE 500 row records.

The fact is that in GLIDE “sometimes they are all there and sometimes they are not.” This is leading us to the fact that in this prototype we are checking, for example, formulas with summations of certain fields, but given that the number of records “appear” and “disappear” these summations vary (since they add up well but do not add up all the ones that should be …) and it generates uncertainty about why it happens???
I don’t know if it is due to update or synchronization times between EXCEL and GLIDE???
And of course what to do???

Thanks in advance.

Greetings,
Javier

[Jeff_Hager]

Which Glide plan are you on? What is the total number of rows in all of the combined tables that are being used by the app?

[Javier_SBT]

Thanks @Jeff_Hager
I am in the GLIDE test plan to make a prototype and test it and see if functionally it is what we want to build. There are about 500 rows (we have taken and loaded directly into Excel the real example data that we would load).

Could it be because it is in the test version that what happens to us??? It would be a relief to know that’s why

Thank you
Javier

[NoCodeAndy]

@Javier_SBT - Are you on the Business Plan free trial?

If so, you should open a support ticket with our team. They’ll be able to go into more detail to troubleshoot the specific app you’re working on.

[Jeff_Hager]

I don’t agree with the way Glide handles this with external data sources, but essentially they will only sync the number of rows that your plan allows. If you have 5000 rows of data in Excel, but your plan only allows 500 rows, then they are only going to sync 500 random rows across all tables. In addition to that 500, they will at least load a minimum of 10 rows in each table, so at least they are not empty. And unfortunately, it seems that the rows that are loaded randomly change day to day.

It does make it really hard to test and prototype, especially when data is missing that is required to build some of the screens. I’ve had to push off projects or update my plan, just so I can build my project. Unfortunately I’m using production data, so I can’t just delete rows. I talk more about it below.

@Jeff_Hager

• I’m trying to rewrite a Legacy Plan Classic App as a New App on a new Starter team plan. I only upgraded the plan on the new team so it’s slightly less annoying to build the app with a bunch of missing data. For whatever reason, Glide will not sync all data from external sources if the plan row limit is too low. I’ve never completely understood the logic behind this. My data is in Google Sheets and I intend to keep it that way. Right now my data far exceeds the row limit of the plan as it’s linked to a legacy app that doesn’t have the current row limits. I understand that I would not be able to have a functioning published version of this new app due to row limits. I’m working on processes to clean up old data in the time being. But the problem is that it’s very hard to build the app when a lot of the crucial data is missing from rows that are limited to only 10 random rows on seemingly random tables. Most of my data is heavily reliant on relations to other tables. I also have resource tables that store global images, choices, etc. and it’s hard to build the interface when that crucial data is missing, since many things do not display properly if there is not associated data. Also, what’s accessible seems to change randomly so it varies from day to day. In my opinion, ALL data should at least sync to the builder so we can at build our projects. I can’t tear into my data to reduce rows since it’s also being used on a published legacy classic app. I know this is a very rare case these days and this is largely my own problem due to having legacy apps. However, I’m not in a particular hurry to rewrite the app, and some hard stop features just aren’t there, so right now I’m picking away at it as I have time and as new features become available, but meanwhile I’m paying for an app that won’t be published anytime soon. I know I’m in a weird situation for many reasons due to still having legacy apps, and when they eventually get migrated to team folders, it will be different story, but overall it seems to make more sense to sync ALL external data regardless of plan limits. Only for the fact that it could allow people to build faster, see the fruits of their effort, and upgrade to a higher paid plan sooner.

I’ve seen several posts where people get confused as to why all of there data is not syncing. Seems beneficial to at least show all data, but still apply restrictions to the published app.

[Javier_SBT]

Thank you very much @Jeff_Hager for the content of your response. Take note ;).

Thank you
Greetings,
Javier

[Javier_SBT]

Thanks @NoCodeAndy

Javier