Creator fields and its applicable operators
Arithmetic operators:
Used to perform mathematical operations on numerical values and concatenate operations on text values.
| Data Type | Field (Operand 1) | Applicable Arithmetic Operators | Applicable Field Types (Operand 2) | Response |
Text |
| + |
| When the '+' operator is applied between a text type field and any applicable type field, the values get concatenated. For example:The following example adds a single line field that gets the username of an email address and a dropdown field that lists the supported domains. Let's assume 'shawn13' and 'zylker.com' are the input username and domain respectively. info username + "@" + domain; //returns shawn13@zylker.com Note: For File-upload, Audio, Video, and Signature fields, the file name will be concatenated to the input text, and for the Image field, the image HTML content will be concatenated. |
Number |
| + |
| When the '+' operator is applied between a number type field and a text type field, the values get concatenated. For example: Consider the following scenario where you need to combine the address number and street name. The following example adds a number field with the single line field. Let's assume '101' and 'Elliot Avenue' are inputs of address number and street. Info Number + ", " + Single_line_field; // Returns, 101, Elliot Avenue. Note: For the look-up field, the record IDNumber) will be stored as its value. |
+ - / * % |
| Follows the arithmetic rules. Performs mathematical operations based on the operator used. Note: For the lookup field, the record ID(Number) will be stored as its value. The ID number will be used for arithmetic operations depending on the operator used. | ||
Boolean |
| + |
| When the '+' operator is applied between the decision box field(true/false) and the text type field, the values will be concatenated. For example: Let us consider a decision box and a single-line field. Assume the decision box is 'on', and 'text' is the input of the single-line field info decision_box + single_line; // Returns truetext |
Decimal |
| + |
| When the '+' operator is applied between a decimal type field and a text type field, the values get concatenated. |
+ - / * % |
| Follows the arithmetic rules. Performs mathematical operations based on the operator used. | ||
List |
| + |
| When the '+' operator is applied between the list type field and a text type field, the values get concatenated. Note: For the Lookup-Multiselect field, the record ID Number) will be stored as its value and it will be concatenated with the text value. |
Date-Time |
| + |
| When the '+' operator is applied between the list type field and a text type field, the values get concatenated. |
Relational operators:
They compare two given values and return a boolean value as a response. They are more commonly used in conditional statements.
| Data Type | Field (Operand 1) | Applicable Relational Operators | Applicable Field Types (Operand 2) | Notes |
Text |
| == != |
| In File-upload, Audio, Video, and Signature fields, the file name will be stored as a value in the field, and for the Image field, the image URL will be stored. These file names will be used for comparison. For example: Consider a File_upload field, the name of the file uploaded in this field is ' File.pdf'. Let's compare this field with a single line field of value ' File.pdf' info file_upload == single_line_field; //Returns true, as the value in the single line field and the value of the file upload field, are matched. |
Number |
| < > <= >= == != |
| In the look-up field, the record ID (Number) will be stored, and that ID will be considered as a number for comparison. For example: Consider a lookup field 'Lookup_field' with the value '12345678910' and a number field 'Number_field' with value '123'. On comparing these values, info Lookup_field == Number_field ; // Returns false. info Lookup_field > Number_field ; // Returns true |
Boolean |
| == != |
| The two boolean field values will be compared. For example:Consider two boolean fields, ' Decision_box_1' and ''Decison_box_2' of values, Decision_box_1 in true state Decision_box_2 in false state On comparing these two fields, info Decision_box_1 == Decision_box_2; //Returns false info Decision_box_1 != Decision_box_2; // Returns true |
Decimal |
| < > <= >= == != |
| The values in these fields will be considered as numbers and compared. Depending on the operator used, the boolean value will be returned. For example:Consider Two percentage fields 'Percentage_field_1' and 'Percentage_field_2', of values 60.0 and 70.0, info Percentage_field_1 > Percentage_field_2 ; // Returns false. info Percentage_field_1 < Percentage_field_2 ; // Returns true. |
List |
| == != |
| Comparing the list with the text data type For example: Consider a Multi_Select field 'Zoho_Product' and a single_line field 'Keyword' with values, Zoho_Products = 'writer', 'sheets', 'crm' Keyword = 'writer' Now, let's compare these fields. info Zoho_Products == Keyword ; // Returns true, as the value of Keyword is listed in Zoho_Products. Comparing list with list data type If a list type field is compared with another list type field it will be treated as a text. For example:Consider a checkbox fields 'Zoho_Products' and 'Keyword' with values, Zoho_Products = 'writer', 'sheets', 'crm' Keyword = 'writer', 'crm', 'sheets' Now, let's compare, info Zoho_Products == Keyword ; // Returns false, as they are not in the exact same order. |
| == != |
| Comparing the list with the number data type In the look-up field, the record ID(Number) will be stored as a list and it will be compared. For example:Consider a Look-up Multi_Select field 'Lookup_Multiselect' and a Number field 'Number_field' with values, Lookup_Multiselect = '4359134000000146007', '4359134000000148007', '4359134000000151005' Number_field = '4359134000000148007' Let's compare info Lookup_Multiselect == Number_field ; // Returns true, as the value of Number_field is in the list of Lookup_Multiselect. Comparing the list with the list data type On comparing the Lookup-Multiselect field with another list field, it will be treated as a text. For example: Consider two list type fields 'Lookup_Multiselect' and 'Checkbox_field' with values: Lookup_Multiselect = '4359134000000146007' '4359134000000148007' '4359134000000151005' Checkbox_field ='4359134000000151005' '4359134000000148007' Let's compare, info Lookup_Multiselect == Checkbox_field; // Returns false, as they are not in the same order.. | |
Time |
| < > <= >= == != |
| If a time field is compared with the date-time field, only the time value from the date-time field will be considered for comparison. Note: A Time field cannot be compared with a Date field. |
Date-Time |
| < > <= >= == != |
| If a date field is compared with the date-time field, only the date value will be considered for comparison. If a date-time field is compared with the time field, only the time value will be considered for comparison. Note: A Date field cannot be compared with a Time field. |
Logical operators:
Typically used with multiple conditions in the criteria. Each condition returns a boolean value, and the logical operators used to connect the conditions determine the overall boolean value of the criteria.
For example: Consider a number field 'Experience' which contains the experience of the candidate. Let's set criteria to check whether the candidate has experience between two-to-four years.
Experience = 3; Response = (Experience > 1) && (Experience < 5) ; //returns true, as the experience of the candidate falls within the criteria.
| Data Type | Field (Operand 1) | Applicable Logical Operators | Applicable Field Types (Operand 2) | Response |
Boolean |
| && || ! |
| Follows boolean laws. |
Note:
- Prediction field's data type changes dynamically with respect to the predicted value in the field. For example, if the predicted value is a text, the field behaves like a text type field.
- Subform field is an advanced field type, which contains fields of varied data types. So, a subform field does not take any data type as such. However, we can refer to the fields in the SubForm as <SubForm_Name>.<SubForm_Field>.
- Section is not meant to collect data. So, it does not take any data type.
- Formula field can contain expressions which can resolve to any one of decimal, number, text, boolean, date-time or time values. Hence, the resultant expression's data type will be the data type of the formula field.