Thanks for your reply. I’m pretty sure in these 2 weeks most delay issues reported to me were over 1h and that’s not user-friendly. And that’s impossible to update everything on Softr bc most fields are formula / linked fields. I will DM your my 2 app ID but if resetting to the old version will my updates in the app or my subscription be removed?
By bringing you back to our old Airtable mechanism, there will be no retroaction in any way. It’ll just read your data in Airtable, and show it in Softr like normal.
@visionist thanks my friend. Send me your APP ID and we’ll return you to the way things were while we update and improve things on our end. We will get it there, just finding more areas that we need to improve and need a bit of time to do so.
It’s odd to me that adding, updating, and deleting all data in Softr seems to be treated as the typical case. And adding, updating, and deleting in Airtable (manually or via API) is being treated as the edge case. Surely reality must be the other way around.
@DustinL the formulas not being updated in Softr properly are an edge case. The other CRUD actions that you outlined are not and have been integrated into our updates and we’re working on improving.
I’ll say that the majority of our other data sources are also using this caching method for most of the year and we’ve had a lot of success with it. So I think this is more about fine tuning the experience for airtable as more feedback + data comes in from our users.
And this updated datasource method will be a big help to improve performance, among many other benefits.
So our hope is that once we implement some of the feedback we’ve received here, and other, that you all will see an big improvement to using Airtable as a datasource, even with its limitations as a non-performant API.
Just hang in there with us, share what you’re experiencing, and we’ll make it great again. Appreciate all of your help!
Try applying filters directly on your graphs to exclude old data.
Consider pre-processing the data in a dedicated “data processing” table before pushing it into the main table that is displayed to customers. By doing so, you can insert clean, updated data as a new record in Airtable, which should then be reflected in Softr.
Is a bit of an annoying workaround, and it does make editing data after it’s been pushed as a new record trickier. Still, it might work for your use case while softr works on a fix.
Can you give an estimate on the timeframe we are looking at? I assume it has high priority as my gut feel tells me that a lot of your customers rely on airtable.
We’re currently on it with several engineers. Hopefully by end of week we will have most items addressed/improved, and then some edge case things like formulas not being updated in a proper manner, updated and fixed next week.
When Airtable is updated independently (not through the Softr app) it’s true that the updates take a few minutes to get reflected in the Softr app. I’ve noticed that manual page refreshes are not required. I kept refreshing to no avail. Then while I was just sitting there staring that the page, it reloaded itself and refreshed the dynamic block’s data with that from Airtable.
But what I also notices is this - I have another block underneath my dynamic data block, whose visibility is conditional and depends on belonging to a group. The group, in turn, has a condition that returns “true” only if the data in Airtable is present.
So, what I noticed is that Softr is smart enough to auto-refresh the dynamic block’s data, but isn’t smart enough to also refresh the other block’s conditional visibility that is now being met (data is present in Airtable). The latter did, indeed, require a manual page refresh.
So, I guess my ask to team Softr would be - as Softr refreshes the blocks to show Airtable’s latest data to also refresh all the page blocks’ conditional visibilities that may be based on the Airtable’s data, too.
Our team just aligned on this and wanted to share a quick update.
If you noticed a delay in Airtable data syncing earlier today, that issue has been resolved. We identified and fixed a delay in our Airtable sync process, and things should now be back to normal.
We’re still actively working on improving sync performance for read-only fields, including formula, lookup, and rollup fields . That work is in progress, and we expect these improvements to be completed sometime next week.
All other Airtable actions (create & update) should continue to sync within a couple of seconds.
Thanks for your patience, and we’ll keep you posted if anything changes.
I’ve noticed that item details blocks seem to be the most effected by these issues - list blocks are functioning as normal. Does that mean that changes have been made to details block that haven’t yet been made to list blocks, and therefore we should anticipate these issues popping up on lists in the future? Or will lists continue to function they way they currently are?
Example: I exposed a formula field on a list block. I have a button on the list block that opens the item details, where I also have that field exposed. I updated the formula, and can see the updated output on the list block, but the details block is still showing the old output.
What is the implication of using a view on a block (in the context of what you said)? I noticed that when I add a new grid or list block, I no longer have the option to select a view. Is that option going away?
Hi I notice there’s an update in Airtable integration: Airtable data source updates now live! - #7 by bornaware . While the live agent said they don’t have a doc currently, it’s fantastic like the inline editing. I asked Jj to reset my apps to the old version several days ago to temporarily avoid the issues mentioned in this topic so I can’t check if this update fixes these issues. If it does, I can’t wait to update to the latest version. Can someone tell me?
I don’t see an update on this, and my client is letting me know they are seeing related issues with data not being synced from Airtable - mostly in regards to formulas.
Has this been addressed, and if not, any new time estimates? @Jjenglert
I’m also experiencing this issue with a Lookup Field. I thought I was losing my mind because functionality that worked no longer does. Looking forward to the updates which I saw mentioned should be this week.