Catalytic fields always have a field type. For example, a field with the type “Text” accepts all alphanumeric characters, and the type “Integer” only accepts whole numbers. There are 11 commonly used field types.
You can specify the field type when you add a field to a Workflow or data table.
In many processes, field data must be converted into new forms. For example, field formulas always output to text fields, even if the result is a whole number—It’s typical to convert field formula output fields into integer field types to use as an input for another action.
There are 5 actions that are useful for converting between field types. Choose the best action based on your desired destination field type. These actions output a new field in the chosen field type.
For example, use the Set value of a integer field action to convert a field into an integer type field. When you configure the action, the input goes in the Output field value field.
- Field: Set value of a decimal field
- Field: Set value of an integer field
- Field: Set value of a text field
- Dates: Set value of a date field
- Field: Set the value of a multiple choice field
Date and date-time type fields have specific actions that help convert back and forth between types:
If incorrectly formatted data is added to a field, a fix task is created. For example, if an action attempts to add the text
Apple to an Integer type field, this will create a fix task.
You can manually change a field’s type if necessary, such as cases where an imported table’s inferred field types are incorrect. Update the field type from the configure field page.
Changing a field’s type may result in unexpected changes to any past data the field collected and stored. For example, if a integer field is changed to true or false, all historical values will change to false.
With how field types are designed, it is recommended to test these changes outside of a production environment to verify all changes are acceptable. Use versions when possible to prevent data loss.