Field configuration lets you specify how the values for your fields are determined. For example, you can set up a form field called "Status" to be a dropdown list with "Standard" and "VIP" as options. Or, you can have have the "user_id" parameter for your HTTP function populated from the "id" column when a user selects a row in your Users table.
Field configuration plays an important role in determining how your tool will function, and understanding all the options below will help you build better, easier-to-use tools.
Specify where the value for each field should come from. Values must be valid for the field type (integer, string, etc). The options below may vary depending on the field type or component.
1) No, have the user complete the field: (nothing pre-filled) Use this option when potential values are unknown.
2) Set a custom default value: Use this option when you have a specific (non-variable) value to set this field to.
3) Pre-fill with a value from a component: Use this option when the data you want exists in another component in the Space. Connecting components together ("binding") lets you create more powerful, time-saving tools.
4) Set a UUID: Use this if you want Internal to generate and set a new universally unique identifier as the prefilled value for this field.
5) Set (default) to null:
6) Set date and time when form submitted or button clicked: (Only available for date-time fields)
You can specify the format in which your field will appear, like paragraph text or dropdown. This option does not appear for buttons or hidden fields in a form, as those components do not allow for manual input.
The available options will change based on the field type.
1) Single line text
2) Paragraph text
Create dropdown options by inputting what you want displayed (Red Ball, Purple Shoe), a comma, and then the value you want to submit (redball, purpshoe). Each option gets its own line.
5) Radio button
Radio buttons are created in the same way as dropdown options.
Allow this field to be blank: Null, undefined or empty strings are allowed as an input to this field. This applies whether the user leaves the field blank, the prefilled value from another component is blank, or the default value is left blank.
Treat blank values as null: Attempts to save empty strings as null values.