Skip to main content

Field Properties

After selecting the appropriate control, you need to configure the properties of the field. Each field can be configured with the following basic properties.

  • Field Name (Hide or not)
  • Required
  • Repeated entries are not allowed
  • Default Value
  • Read-only
  • Hide
  • Hide when adding record
  • Width
  • Color and style of field name
  • Hint Text
  • Field Description
  • Field Alias
  • Notes to Field

Field Name (Hide or not)​

An appropriate field name helps to better identify the field content. Sometimes it is not necessary to show the field name when displaying, only the content, so you can hide the name.

Default Value​

When adding a new record, you can set the default value of the field to auto fill it into the field, either the static default value or the dynamic default value.

More details about default value

Required​

If a field is set as required, when editing a record, if the field is empty, it cannot be saved and there will be a prompt. When editing in a sheet, or when writing data through workflow and API, or when importing data through Excel, there is no requirement checking, and the field can be written normally if it is empty.

Force checksum on write​

If only [Required] is checked, there is no requirement checking when importing data or writing data through workflow. If you also check [Force checksum on write], there will be checking when writing data through workflow and API, and importing data through Excel, and if the field is empty, the record can't be written. The specific rules are as follows:

  • Workflow: the workflow stops and report the error.
  • Import via Excel: Skip the data that does not pass the check, and import the other data normally.
  • API: Failed to write, and return an error message.
  • Data Integration Sync: Skip the data that does not pass the checksum, and sync the other data normally. The skipped data does not count the number of writes.

Repeated entries are not allowed​

Some fields, such as job numbers, are often unique, so when adding or editing records, if you enter duplicate data, there will be a prompt and cannot be saved.

It checks for duplicates only when editing fields, not when importing data or writing data through the API. You can create unique indexes to ensure that the content of the field is absolutely unique.

Read-only​

If read-only is checked, the field cannot be filled directly when adding or editing records. However, it can be modified to editable through workflows or business rules.

Hide​

If [Hide] is checked, the field is always not displayed when adding or editing records. Such fields can be used as bridge fields, which are only involved in calculations and do not have to be displayed to users.

Hide when adding record​

If checked, the field will not be displayed when adding records, but will be displayed when viewing and editing records. For example, in an Employee worksheet, there is a termination field, but when adding an employee, this field is not needed, then you can check [Hide adding record].

Width​

In the form, you can put up to 4 fields each line. The shortest field can be set to 1/4 the width of the entire line, and the longest can be the width of the line.

Color and Style​

You can set the color, font size, and font style for field titles.

Hint Text/Field Description​

They can help users understand what needs to be filled in the field.

Effect:

Three ways to display field description

  • Auto

    The description text is displayed below the field when creating a record and in the icon when viewing a record.

  • Icon

    The description is always hidden in the icon and is displayed when the cursor is moved over the icon.

  • Text

    The description is always displayed below the field.

Field Alias​

The system automatically generates a field ID (24 letters and numbers) for each field, which is mainly used for API interfacing and development, and for unique identification of fields in Word and Excel printing templates.

Since the field IDs are not readable, users cannot quickly understand the meaning of the fields. Moreover, after copying the application, the field IDs will also be changed, so you need to reconfigure them when interfacing and development.

You can replace the role of the field ID by setting an alias for the field, which will be much easier for interfacing and development.

Entrance to Set Field Alias:

  • Form Settings

  • API Documentation

Notes to Field​

Just as the code needs notes, the notes are primarily for the developer's convenience in maintaining the application and are not displayed when the user creates and views the record.

Have questions about this article？ Send us feedback