Implement the ability to preserve screen components when changing the selected source table on the screen in the builder with a custom style. Keeping the components intact would ensure a smoother, more seamless workflow, allowing editors to make changes to the selected source table without losing current component configurations.
or maybe provide “Use Last Screen Configuration” vs “Use Default Screen Configuration” options when creating a new screen.
It is difficult to preserve components when the underlying table is gone - column names are different, etc.
A warning should come up that you will lose all your components when changing a screen source. I may have put that in as a Feature request since this has bitten me more than twice.
Best practice is to copy/duplicate the current tab/screen before changing the data source. Make the change and then paste in the components and see what Glide recognizes.
In the future maybe this is something for AI?
It would be nice if you could change the source without having to redo all the components.
This issue happened to me a number of times when using the same table as the source. Including the problem where innocently changing a setting causes all of the components to disappear.
But with respect to the mechanism of using last components, why must it be connected to the data? A component can be added in an empty state, right?
I use this method too because I don’t know of another way at the moment.
I found a workaround solution!
- Duplicate screen
- Change the source on your screen
- Right click the components In the duplicate screen → copy
- In the main screen, paste the components one by one.
Edit: thanks @MattLB Preserve screen components when switching the screen source table in a custom style - #3 by MattLB
yes, similar to what @MattLB said. We’ll use these workarounds until Glide gives us a simple toggle option.
Thanks ! You are right, missed that post
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.