There seems to be a bug or issue with the new form builder. In my case, to keep design consistent in my projects I have created various input components.
When I try to use these, the variable is not appearing. If I try to use regular input fields that are not components, then it works.
This is causing a little headache with me, as it seems that I need to build forms without components, and that means it’s a lot more challenging to keep design and logic consistent in the application.
Anyone else experiencing this issue and have figure out a way to resolve it? I contacted support, but they said it’s a limitation that they can’t resolve currently.
Since nobody came with a good solution, I would advice you to take a look at the ‘Starter kit’ project template > form builder. They have something that you could start from to build what you need.
Hmm, still having issues. Field components don’t seem to get picked up by Form Containers. Anyone able to replicate this? Curious as to how everyone is doing CRUD without this.
If I remember correctly, take a input component you created and move it inside a form, then click “Edit” on the input component and you should be able to see this field. Give it a name and it will show up in the "local inputs” of the form
Actually, I think it is just because the Starter Kit Components use outdated inputs that don’t support this. If I replace the inputs, the panel seems to show.
Having done some further experimenting, I think I have the steps for getting your custom inputs working with form container:
Start with the ‘Starter Kit’ inputs as your base. This gives you the component proporties, variables and workflows you will need.
Import one of the starter kit fields so that you can look inside the component. You’re going to need to replace all the inputs inside of it with new base inputs because they will be missing the ‘Form Container’ panel which makes the input compatible.
When you create a new input all the proporties and variables will carry over, so the only thing you’ll need to copy is the workflow called ‘Update exposed var and emit event’ (title will vary slightly based on the specific input).
Now the part that ensures it is compatible with the form container:
go to the form container section on the third tab of the input.
bind field name to something that will be unique for each input (I chose ‘label’)
set custom validation to ‘yes’
bind validation to ‘value.valid’.
Hopefully this helps someone in future. Inputs are not as simple as you might hope.
~~