Hey George. It seems to be working for iOS but still glitchy on Android (some pics take while others don’t).
Even if forms work in modals, then there’s the problem of all blocks on the parent page updating to reflect the record added. Softr has been dangling Airtable “syncronization” since last year, which sounds like a solution, but unlikely anytime soon with their new in-house database. Artur also flaunted conditional fields when adding items to list blocks, but I doubt this will get done either. Please let everyone know if you find a solution to adding records using conditional relationships. Thanks!
Thanks Ben. Yeah we use custom code for all conditional form pages to update parent pages and sometimes blocks in the same page as the form.
We rarely use add record actions as it doesnt have conditional logic for our various user avatars so no good.
Yes you can set them up in the custom code header page and update ALL blocks in parent page from the page youre making the update from (this is the page where you have conditional form for example). @matthieu_chateau has alot of posts and updates them regularly if any changes were to occur.
@Jjenglert The Softr/Airtable upgrade in a couple months is going to remove the need for these custom codes right?
We use conditional forms to update parent pages and sometimes blocks (like a table) in the same pages as the form. We currently use custom code to refresh the updates but i think thats not going to be needed going forward eh?
Right. Custom codes are useful to an extent, but with how slow Softr is with Airtable dynamic blocks, Softr has always rendered even slower with them. If this works the way Artur says, it should update all blocks on the parent page under modals. We’ll see if this works, if and when it gets released.
We’re about 1 month out from that release still. Work is in progress and is looking good. Aiming to get this update into all of your hands ASAP. It’s a BIG one.
Thanks for your note. We’re no longer developing new features for legacy blocks, as the infrastructure behind them is outdated.
Instead, we’re rebuilding the blocks we plan to keep — like list, table, grid, kanban, etc. — on a more modern foundation that offers better performance and compatibility with upcoming features.
Airtable DSV2 will still work with legacy blocks, but they won’t benefit from improvements like faster refreshes or enhanced speed, since they’ll continue using the original Airtable connection.
Airtable DSV2 is the technical name for the upgraded Airtable connection that we’re building (We’ve also called it data synchronizer as well).
Essentially, it caches your Airtable data, which allows for a unified data model that we can use for faster performance, data standardizations, and many other things.
That is what I thought. Lots of new and unconventional terms thrown out there for the same feature. Thanks for the clarification.
Since Softr makes legacy customers upgrade for their new Database limits, I have to ask. Will Softr be charging more for caching our Airtable data? We are not looking forward to any more surprises this year.
No, if you continue to use Softr with Airtable, nothing changes. You can just enjoy the enhancements of this integration.
It’s when you want to use Softr interfaces with Softr Databases that changes things cause at that point, you’re removing Airtable and adding Softr Databases as a new product there.