How to use the Format Data Set window
The Format Data Set Data window lets you customize how each column appears and behaves in the app:
-
Update the label to make the field name more user-friendly.
-
Set the data type (such as text, number, date) so the field works like a standard input in tables.
This helps ensure that users enter information that matches the format and requirements of the original system—reducing errors and keeping your data consistent.
- On the Data Set Designer page, click Data Set Properties next to open the Format Data Set Data window.
- The Source Name field displays the name generated from the data set.
- Enter a label for the app user in the Label field. If you enter a duplicate label, it will be numbered.
- Select the type and options for each field. Types include Checkbox, Date, Lookup, Long Text, Number, Radio, Select, Text, and Time. Depending on the type you select, the options for the field will vary.
These settings are not editable when designing the form. If you must make changes, you need to do it here, then fix your form. We recommend testing your data set on a test form before creating forms you want to use. - Mark Hide on Form if the default field on the form is hidden. This controls how it is defined on a form and cannot be changed by the form designer. You might use a hidden field when you have a GUID or other type field that is part of determining your data set but isn’t useful for the form user.
- Mark Editable if the field on the form is editable. Editable fields will automatically update the data source when the form is submitted. Be careful to only mark this for fields that the source allows edits on. Some key fields should not be marked editable because of the other purposes they serve.
If you need different settings for hidden and editable fields on different forms, create a second data set with those setting changes and use it on the different form. - Click OK to save your changes and close the window.
Note: Be careful when setting up this information. The data types are not verified that they match, so the integration could fail. For example, do not have a Select input with a Number input.