Introduction
...
There is a differentiation between textual to numeric fields. The user has to select “numeric” or “textual” in the calculated fields toggle, depending on the required calculation. As a result, different fields will be available for each type of calculation engine. Only system parameters which return numeric values will be available in the numeric engine, while in the textual engine all fields will be available (but will be considered as strings).
The engine is case-insensitive when using functions names.
Supported Mathematical Functions
...
Function | Explanation | Examples |
|---|---|---|
| The function will display the smallest/largest number between two or more conditionsfields or numbers | Min(unit_id; 1000) |
AVG | The function will display the average between two or more conditionsfields or numbers | AVG(a1; a2; a3; ...) |
ABS | The ABS function returns the absolute value of the given number | ABS(-10) |
| The “IF” function is a decision-making condition function between numerical fields. |
|
...
Advanced Textual functions
You must use a semicolon (;) sign to separate the clauses in the equation instead of a regular comma. The "combined" condition must be accompanied by parentheses in order for it to function properly.
IF(('unit_is_stationary' = 'Yes') && ('unit_is_stationary' = 'Yes'); 'OK';'Not OK')
Function | Explanation | Examples |
|---|---|---|
SWAP | The function will convert a numeric field to a text field | Swap(’real_time_status’ ; ‘0:Down’ ; ’999:Off Grid’) |
| The “IF” function is a decision-making condition function between textual fields. IF operation – syntax: IF(‘a’ ; ’b’ ; ‘c’) -> if “a” is true then “b” else “c”. We support the following Boolean operations in text fields: ‘a’ = ‘a’ -> True ‘a’ != ‘a’ -> False |
|
...