I am not sure exactly when this started, but as of this morning, my ARRAYFORMULAs in Google Sheets are no longer working. Only the row that contains the actual formula (first row) will sync.
When I remove the ARRAYFORMULA and drag the formula down, it works properly again. This is fine as a workaround but not an ideal solution long term.
Any thoughts? I haven’t changed anything on either end…
Wouldn’t it be better to use Relation/Lookup or Query/SingleValue in Glide? It would be a whole lot more responsive (instant) and you wouldn’t have the delay of waiting for the result from the VLOOKUP to sync back to Glide and back to your device.
OK. Just for clarification, is it true that the ArrayFormula appears to be working when you view it in the google sheet, and the issue is only that it does not sync all of the data in that column to Glide?
In my experience I’ve had issues in the past where my google sheet did a lot of heavy calculations (several minutes to process), and if Glide did a sync in the middle of those calculations, it did not get the latest data. I still have some things that I can only achieve in google sheets (or I can do it in glide, but would suffer a huge performance hit), so I use a handful of arrayformulas, import range, vlookups as well. But the things I’m doing don’t necessarily rely things being synced back to Glide instantly. Over the years I have moved a lot of computed logic into Glide, which has solved a lot of my problems because the google sheet performa it’s calculations much more quickly.
If you resync the data via the data editor, does it pull in the values?
That’s right, everything works fine in the Google Sheet. When I manually sync Glide, it still doesn’t pick up anything but the first row where the actual ARRAYFORMULA is located.
I definitely agree with your thoughts - medium / long-term we are likely to migrate this app to either Glide Tables or potentially a SQL data source so I will work out better solutions to issues like this at that time, or they’ll resolve themselves. But, we have to work out some things internally before I know what directly we’re going in so I don’t want to make a bunch of major changes before we get that figured out…
Hopefully @NoCodeAndy can get you straightened out. I was about to suggest that maybe it’s a bug related to the other recent reports. I’ve been nervous about some of these recent issues, but so far I’ve been lucky, or just haven’t noticed yet.