It will be great if for pages will exist a container that can have a grid display in multiple columns, so we can put more fields in a row.
As an example of doing that, have a look at Airtable Interfaces … they do a pretty good job with this when building an Interface and I believe the same concept could work also here.
Please visit https://staging.heyglide.com/ (our test server) and try the
For Each container.
We’d love your feedback on it.
@david For-each container is a great functionality to have an action for each element … so definitely is something useful, but it would be great to have a concept similar to that one inside the form container or at least the form container to be able to have the Layout options as currently, the form can be displayed only in a single column.
Thanks for the staging link … if you have other new things coming that you need some feedback … let me know.
You can have multiple columns in a Form screen. All you need to do is set the target to “Current” or “Main” and then add a container with the desired number of columns - up to 4.
I was referring to the number of columns in a form container to be able to have the form elements in multiple columns … could this be done also ?
Yes, as I described.
I tested exactly that before I posted my reply to be sure that I wasn’t giving bad advice
@Darren_Murphy , in this case I’m not really sure how to do this in the form container … can you please explain … if you are referring to a new form screen with a custom container in it and adding all the elements in the columns and then a button to submit all the fields, I know it can be done, I was just hoping that it can be done also for the form container as it’s easier to maintain … so please, let me know how to do it
oh, Form Container!
Sorry, my bad. I did give you bad advice after all. I was reading Form Screen and not Form Container.
No, you’re right. It can’t be done in a Form Container.
Having said that, using a Form Screen instead is a pretty simple alternative, no?
Yes but the experience and functionality is not exactly the same as you have to recreate all the fields the functionality of the submit button and I think there might be also other downsides … put in terms of achieving that, of course you can achieve it … but with a workaround … that’s why it would be great to have it in the container also.
I’m not sure why you’d consider that a workaround.
Functionally, a Form Container and a Form Screen are more or less the same. Both give you a set of default input components based on the selected target table. Both will add a row to the selected table when the form is submitted. The only real difference is that a Form Container is embedded in the current screen, and a Form Screen gives you a new screen/overlay to work with.
Below is a screen shot that shows a Form Container on the current screen, with a Form Screen in an overlay screen on top (which was triggered by the “Open Form Screen” button). Both are targeted at the same table, and each has an identical set of default input components.
I’d argue that a Form Screen actually gives you more flexibility, not less.
I agree but in order to have a form screen you need to create another action before in order to be able to display that screen … not a big thing, but it’s not something that can be used directly on a page under a submenu item … that’s why I consider a workaround … it’s still a solution but from a UX point of view you need to have one more click.
@david we are really in need for this feature it will change the way we display data for our clients