- Aggregate
- Comparison
- Info
- Logical
- Lookup
- Math
- ADD(augend, addend)
- DECIMAL(value)
- DIVIDE(dividend, divisor)
- INCLUDES(multi_select_dropdown, api_name)
- INTEGER(value)
- ISPICKVAL(dropdown, api_name)
- MINUS(minuend, subtrahend)
- MOD(dividend, divisor)
- MULTIPLY(multiplicand, multiplier)
- POW(base, exponent)
- POWER(base, exponent)
- UMINUS(value)
- UPLUS(value)
- Text
NOTE: When listing types a function accepts, the notation here uses the non-standard character *
to represent a wild card that can be any type supported by formulas. When multiple *
's are used, they still represent any supported type, but all *
's must have the same type. For example, the notation IF(boolean, *, *) -> *
translates to: The function IF
takes three arguments, the first of type boolean
, and the second and third of any supported type, provided the types are the same. The function returns a value of the same type as the second and third arguments. In more standard notation, it is equivalent to <T>IF(boolean, T, T) => T
.
Returns the sum of a series of numbers
value
- A series of numbers
=SUM($aggregate_set.related_numeric_field)
=SUM($related_account_set.revenue)
SUM(integer list) -> integer
SUM(decimal list) -> decimal
-
Not supported in formulas used for validations
-
Only currently supports summations using an
ACCESS
using what's known in lanetix as afiber
(often referred to asreferenced by
). This is an object that represents the relationship between two record types. For example, if there is ancontact
record type with apicker
field to theaccount
record type, the relationship representing allcontacts
which reference a particularaccount
using that picker is thefiber
. Note that thefiber
is only associated with (and thus able to be used in formulas on) theaccount
record type. -
Because
SUM
on integers returns an integer, and integers can only represent values from-2,147,483,647
to2,147,483,647
, it is recommend to not use an integer field for theSUM
result, and cast the argument to a decimal:=SUM(DECIMAL($related_account_set.revenue))
Returns TRUE
if two specified values are equal and FALSE
otherwise. Equivalent to the =
operator.
value1
- The first value.value2
- The value to test againstvalue1
for equality.
=EQ(2, 3) -> FALSE
=EQ(2, $field)
EQ(*, *) -> boolean
Equality comparisons for the following types are not supported:
- dropdown (Use
ISPICKVAL
instead) - multi-select dropdown (Use
INCLUDES
instead) - hyperlink
- file upload
- image
- location
- hyperlink list
- file upload list
- image list
Returns TRUE
if the first argument is strictly greater than the second, and FALSE
otherwise. Equivalent to the >
operator.
value1
- The value to test as being greater thanvalue2
.value2
- The second value.
=GT(2, 3)
=GT(2, $field)
GT(date, date) -> boolean
GT(decimal, decimal) -> boolean
GT(integer, integer) -> boolean
GT(string, string) -> boolean
-
NULL
dates are considered to have occurred at the first instance of time, and thus before all non-NULL
dates. -
It is unfortunately not possible to compare integer and decimal fields together without a manual casting the integer field using the
DECIMAL
function. The suggested solution to this issue is incredibly complex, and your understanding is appreciated. -
String comparisons use alphabetical ordering, and are case sensitive. Numeric characters are considered "less than" alphabetical ones, and upper case letters are considered "less than" lower case. Ordering of symbols typically follows the ordering as defined in the unicode specification, but this is not guaranteed. Ordering of symbols between formula fields and formulas as validations may vary slightly.
-
Be aware that string comparisons happen in the order of their characters, so
=GT("1", "05")
will returnTRUE
, because the second argument starts with the text0
, which is considered less than than the text1
. Comparing numbers,=GT(1, 05)
, will returnFALSE
as expected.
Returns TRUE
if the first argument is greater than or equal to the second, and FALSE
otherwise. Equivalent to the >=
operator, or the formula =OR(GT(value1, value2), EQ(value1, value2))
.
value1
- The value to test as being greater than or equal tovalue2
.value2
- The second value.
=GTE(2, 3) -> FALSE
=GTE(2, $field)
GTE(date, date) -> boolean
GTE(decimal, decimal) -> boolean
GTE(integer, integer) -> boolean
GTE(string, string) -> boolean
-
NULL
dates are considered to have occurred at the first instance of time, and thus before all non-NULL
dates. -
It is unfortunately not possible to compare integer and decimal fields together without a manual casting the integer field using the
DECIMAL
function. The suggested solution to this issue is incredibly complex, and your understanding is appreciated. -
String comparisons use alphabetical ordering, and are case sensitive. Numeric characters are considered "less than" alphabetical ones, and upper case letters are considered "less than" lower case. Ordering of symbols typically follows the ordering as defined in the unicode specification, but this is not guaranteed. Ordering of symbols between formula fields and formulas as validations may vary slightly.
-
Be aware that string comparisons happen in the order of their characters, so
=GTE("1", "05")
will returnTRUE
, because the second argument starts with the text0
, which is considered less than than the text1
. Comparing numbers,=GTE(1, 05)
, will returnFALSE
as expected.
Returns TRUE
if the first argument is strictly less than the second, and FALSE
otherwise. Equivalent to the <
operator.
value1
- The value to test as being less than value2.value2
- The second value.
=LT(2, 3) -> TRUE
=LT(2, $field)
LT(date, date) -> boolean
LT(decimal, decimal) -> boolean
LT(integer, integer) -> boolean
LT(string, string) -> boolean
-
NULL
dates are considered to have occurred at the first instance of time, and thus before all non-NULL
dates. -
It is unfortunately not possible to compare integer and decimal fields together without a manual casting the integer field using the
DECIMAL
function. The suggested solution to this issue is incredibly complex, and your understanding is appreciated. -
String comparisons use alphabetical ordering, and are case sensitive. Numeric characters are considered "less than" alphabetical ones, and upper case letters are considered "less than" lower case. Ordering of symbols typically follows the ordering as defined in the unicode specification, but this is not guaranteed. Ordering of symbols between formula fields and formulas as validations may vary slightly.
-
Be aware that string comparisons happen in the order of their characters, so
=LT("1", "05")
will returnFALSE
, because the second argument starts with the text0
, which is considered less than than the text1
. Comparing numbers,=LT(1, 05)
, will returnTRUE
as expected.
Returns TRUE
if the first argument is strictly less than or equal to the second, and FALSE
otherwise. Equivalent to the <=
operator, or the formula =OR(LT(value1, value2), EQ(value1, value2))
.
value1
- The value to test as being less than value2.value2
- The second value.
=LTE(2, 3) -> TRUE
=LTE(2, $field)
LTE(date, date) -> boolean
LTE(decimal, decimal) -> boolean
LTE(integer, integer) -> boolean
LTE(string, string) -> boolean
-
NULL
dates are considered to have occurred at the first instance of time, and thus before all non-NULL
dates. -
It is unfortunately not possible to compare integer and decimal fields together without a manual casting the integer field using the
DECIMAL
function. The suggested solution to this issue is incredibly complex, and your understanding is appreciated. -
String comparisons use alphabetical ordering, and are case sensitive. Numeric characters are considered "less than" alphabetical ones, and upper case letters are considered "less than" lower case. Ordering of symbols typically follows the ordering as defined in the unicode specification, but this is not guaranteed. Ordering of symbols between formula fields and formulas as validations may vary slightly.
-
Be aware that string comparisons happen in the order of their characters, so
=LTE("1", "05")
will returnFALSE
, because the second argument starts with the text0
, which is considered less than than the text1
. Comparing numbers,=LTE(1, 05)
, will returnTRUE
as expected.
Returns TRUE
if two specified values are not equal and FALSE
otherwise. Equivalent to the <>
operator (the alternate syntax !=
also works).
value1
- The first value.
value2
- The value to test against value1
for inequality.
=NE(2, 3) -> TRUE
=NE(2, $field)
NE(*, *) -> boolean
Equality comparisons for the following types are not supported:
- dropdown (Use
ISPICKVAL
instead) - multi-select dropdown (Use
INCLUDES
instead) - hyperlink
- file upload
- image
- location
- hyperlink list
- file upload list
- image list
Returns TRUE
if the value is unknown (NULL
), or is a value that would cause lanetix to display --
in the UI instead of the actual value (or the unchecked checkbox with a line through it).
value
- the value to check for blankness
=ISBLANK("") -> TRUE
=ISBLANK(" ") -> TRUE
=ISBLANK("Not blank") -> FALSE
=ISBLANK($field)
ISBLANK(*) -> boolean
- All types are considered blank if they are
NULL
strings
are additionally considered blank if they are empty (""
), or contain all whitespacehyperlinks
are additionally considered blank if their URL value is empty or all whitespacelist
s are additionally considered blank if they are notNULL
and have no entries- All other types have no special semantics around
ISBLANK
Checks whether a value is an error.
value
- The value to be verified as an error.
=ISERROR(5 / 0) -> TRUE
=ISERROR($revenue / $total_revenue)
Returns TRUE
if all of the provided arguments are logically TRUE
, and FALSE
if any of the provided arguments are logically FALSE
.
logical_expression1
- An expression or reference to a cell containing an expression that represents some logical value, i.e. TRUE or FALSE, or an expression that can be coerced to a logical value.logical_expression2
- Another expression that represents a logical value.
=AND(TRUE(), TRUE()) -> TRUE
=AND(TRUE(), FALSE()) -> FALSE
=AND(FALSE(), TRUE()) -> FALSE
=AND(FALSE(), FALSE()) -> FALSE
=AND($field_1 = 1, $field_2 = 2)
=AND($boolean_field, $other_boolean_field)
=AND($air_freight_checkbox, $revenue > 1000)
AND(boolean, boolean) -> boolean
-
The value
0
and the empty string""
are not automatically cast to booleans like in some languages. To use them inAND
, use an explicit comparison=AND($field_1 = 0, $field_2 = "")
-
Only two arguments can be supplied to
AND
, to use more, nest the additional ands:=AND($field_1 = 1, AND($field_2 = 2, $field_3 = 3))
-
Short circuit evaluation is used, so if the first argument evaluates to
FALSE
, the second argument is never evaluated. This means formulas like=AND(FALSE(), 5 / 0)
will returnFALSE
rather than an error.
Returns the logical value FALSE
.
None
=FALSE() -> FALSE
FALSE() -> boolean
Returns one value if the logical expression is TRUE
and another if it is FALSE
.
logical_expression
- An expression or reference to a cell containing an expression that represents some logical value, i.e.TRUE
orFALSE
.value_if_true
- The value the function returns if logical_expression isTRUE
.value_if_false
- The value the function returns if logical_expression isFALSE
.
=IF(TRUE(), 0, 10) -> 0
=IF(FALSE(), 0, 10) -> 10
=IF($education = "PHD", `Hello Dr. $name`, `Hello $name`)
=IF($boolean_field, "boolean_field is true (checkbox is checked)", "boolean_field is false (checkbox is not checked)")
-
Ensure that
value_if_true
andvalue_if_false
are provided to the function in the correct order - according to google, this is the single most common source of problems withIF
. -
Lanetix booleans are technically tri-state (
TRUE
,FALSE
, orNULL
). In order to keep things simple and not introduce three-value logic in formulas,NULL
is treated as if it wereFALSE
. This has consequences as any related booleans accessed through pickers will be false when the picker they're accessed through is not selected. For example, the formula=IF($picker.boolean_field, 1, 0)
will only evaluate to1
if thepicker
field is selected and the relatedboolean_field
on the picked record instance isTRUE
. -
The case that is not selected is never executed, so errors from it will not propagate. For example, the formula
=IF(TRUE(), 1, 1 / 0)
will evaluate to1
, not an error from dividing by zero.
Returns the opposite of a logical value - NOT(TRUE())
returns FALSE
; NOT(FALSE())
returns TRUE
.
logical_expression
- An expression that represents some logical value, i.e.TRUE
orFALSE
.
=NOT(TRUE()) -> FALSE
=NOT($field = 2)
=NOT(ISERROR(5 / 0)) -> FALSE
NOT(boolean) -> boolean
- Neither strings nor integers automatically cast to booleans, in order to get the usual "truthy" semantics from these types, use explicit comparisons:
=NOT($string = "")
or=NOT($number = 0)
.
Returns TRUE
if any of the provided arguments are logically TRUE
, and FALSE
if all of the provided arguments are logically FALSE
.
logical_expression1
- An expression that represents some logical value, i.e.TRUE
orFALSE
logical_expression2
- Another expression representing some logical value, i.e.TRUE
orFALSE
=OR(TRUE(), TRUE()) -> TRUE
=OR(TRUE(), FALSE()) -> TRUE
=OR(FALSE(), TRUE()) -> TRUE
=OR(FALSE(), FALSE()) -> FALSE
=OR($field_1 = 1, $field_2 = 2)
=OR($boolean_field, $other_boolean_field)
=OR($air_freight_checkbox, $revenue > 1000)
OR(boolean, boolean) -> boolean
-
The value
0
and the empty string""
are not automatically cast to booleans like in some languages. To use them inOR
, use an explicit comparison=OR($field_1 = 0, $field_2 = "")
. -
Only two arguments can be supplied to
OR
, to use more, nest the additional ands:=OR($field_1 = 1, OR($field_2 = 2, $field_3 = 3))
-
Short circuit evaluation is used, so if the first argument evaluates to
TRUE
, the second argument is never evaluated. This means formulas like=OR(TRUE(), 5 / 0)
will returnTRUE
rather than an error.
Returns the logical value TRUE
.
None
=TRUE()
TRUE() -> boolean
Returns a logical Exclusive Or of all arguments. That is, returns TRUE
if either logical_expression1
is TRUE
or logical_expression2
is TRUE
, but returns FALSE
if both are TRUE
.
logical_expression1
- An expression that represents some logical value, i.e.TRUE
orFALSE
logical_expression2
- Another expression representing some logical value, i.e.TRUE
orFALSE
=XOR(TRUE(), TRUE()) -> FALSE
=XOR(TRUE(), FALSE()) -> TRUE
=XOR(FALSE(), TRUE()) -> TRUE
=XOR(FALSE(), FALSE()) -> FALSE
=XOR($field_1 = 1, $field_2 = 2)
=XOR($boolean_field, $other_field = 1)
XOR(boolean, boolean) -> boolean
-
The value
0
and the empty string""
are not automatically cast to booleans like in some languages. To use them inXOR
, use an explicit comparison=XOR($field_1 = 0, $field_2 = "")
-
Only two arguments can be supplied to
XOR
, to use more, nest the additional ands:=XOR($field_1 = 1, XOR($field_2 = 2, $field_3 = 3))
Allows accessing related fields through pickers, system fields through the use of the $lanetix
field, or aggregating related fields through the use of a one to many relationship.
value1
- The field or relationship being accessedvalue2
- The field to access fromvalue1
. If accessing through an aggregatable relationship, multiple values will be accessed and constructed into a list.
=ACCESS($picker, $name)
=ACCESS($lanetix, $id)
=ACCESS(ACCESS($picker, $lanetix), $id)
=ACCESS(ACCESS($picker, $secondary_picker), $name)
It's highly recommended to use the .
operator instead of the ACCESS
function for clarity, as the following are equivalent to their respective examples above:
=$picker.name
=$lanetix.id
=$picker.lanetix.id
=$picker.secondary_picker.name
ACCESS(picker, *) -> *
ACCESS(lanetix, *) -> *
ACCESS(related record accessor, *) -> *
ACCESS(aggregatable relationship, *) -> list of *
- Not supported in formulas used for validations
- Shadow record types (e.g. users) cannot be accessed even though pickers can be created to select them
Returns the sum of two numbers. Equivalent to the + operator.
aguend
- The number add toaddend
- The number to be added
=ADD(2, 3) -> 5
=ADD($field, 2.5)
=ADD(DECIMAL($integer_field), $decimal_field)
ADD(integer, integer) -> integer
ADD(decimal, decimal) -> decimal
-
Any field for which
ISBLANK
returnsTRUE
will be treated as0
-
It is unfortunately not possible to add an integer and decimal fields together without a manual casting the integer field using the
DECIMAL
function. The suggested solution to this issue is incredibly complex, and your understanding is appreciated. -
Literals are auto-casted, which means they might unexpectedly be rounded. For example
=ADD($field, 2.5)
is evaluated as=ADD($field, 3)
iffield
's type isinteger
. This does not apply to formulas used as validations. -
Formulas used as validations use floating-point representation for all numbers. Although quite technical, it is recommended to read and understand the limitations and problems with this representation.
Converts the value to a decimal
value
- The value to convert to a decimal
=DECIMAL(5) -> 5
=DECIMAL($integer_field)
DECIMAL(integer) -> decimal
DECIMAL
can currently only be used on fields - not literals or expressions. Formulas used for validations do not have this restriction.
Returns one number divided by another. Equivalent to the /
operator.
dividend
- The number to be divided.divisor
- The number to divide by.
=DIVIDE(10, 5) -> 2
=DIVIDE(5, 10) -> 0.5
=DIVIDE($field, 2)
=DIVIDE(DECIMAL($integer_field), $decimal_field)
DIVIDE(integer, integer) -> integer
DIVIDE(decimal, decimal) -> decimal
-
Any field for which
ISBLANK
returns true will be treated as0
-
It is unfortunately not possible to divide integer and decimal fields together without a manual casting the integer field using the
DECIMAL
function. The suggested solution to this issue is incredibly complex, and your understanding is appreciated. -
When dividing two integers, the resulting value is rounded to an integer using an away from zero strategy (if needed)
-
Dividing by zero will result in an
#Error!
message being displayed as the value when using formula fields, and the validation being considered failed when using formulas as validations.
Returns TRUE
if the api_name
is one of the selected dropdown options, FALSE
otherwise
multi_select_dropdown
- a multi-select dropdown fieldapi_name
- a string matching the API Name (not display name) of the option to check if it's selected
=INCLUDES($states, "va")
INCLUDES(multi-select dropdown, string) -> boolean
- This cannot be used on single-select dropdowns, use
ISPICKVAL
to check what the selected option is instead. - The second argument must be the API name of the option. Using display names is not supported, as it's possible to have multiple options that all have the same display name, which makes it ambiguous as to which particular option is being searched for.
- To check for multiple selected values, use the
AND
andOR
functions. For example,=OR(INCLUDES($states, "va"), INCLUDES($states, "ca"))
Casts the value
to an integer, rounding away from zero (if needed).
value
- the value to convert to an integer
=INTEGER(10.1) -> 10
=INTEGER(10.5) -> 11
=INTEGER(-10.5) -> -11
=INTEGER($decimal_field)
INTEGER(decimal) -> integer
INTEGER
can currently only be used on fields - not literals or expressions. Formulas used for validations do not have this restriction.
Returns TRUE
if the dropdown's value has the same API name as the api_name
argument, FALSE
otherwise
dropdown
- a dropdown fieldapi_name
- a string matching the API Name (not display name) of the option to check if it's selected
=ISPICKVAL($states, "va")
- This cannot be used on multi-select dropdowns, use
INCLUDES
to check what the selected option(s) is instead. - The second argument must be the API name of the option. Using display names is not supported, as it's possible to have multiple options that all have the same display name, which makes it ambiguous as to which particular option is being searched for.
Returns the difference of two numbers. Equivalent to the -
operator.
minuend
- The number to be subtracted from.subtrahend
- The number to subtract fromminuend
.
=MINUS(2, 3) -> -1
=MINUS($field, 2.5)
=MINUS(DECIMAL($integer_field), $decimal_field)
MINUS(integer, integer) -> integer
MINUS(decimal, decimal) -> decimal
-
Any field for which
ISBLANK
returns true will be treated as0
-
It is unfortunately not possible to subtract an integer and decimal fields together without a manual casting the integer field using the
DECIMAL
function. The suggested solution to this issue is incredibly complex, and your understanding is appreciated. -
Literals are auto-casted, which means they might unexpectedly be rounded. For example
=MINUS($field, 2.5)
is evaluated as=MINUS($field, 3)
iffield
's type isinteger
. This does not apply to formulas used as validations. -
Formulas used as validations use floating-point representation for all numbers. Although quite technical, it is recommended to read and understand the limitations and problems with this representation.
Returns the result of the modulo operation: the remainder after a division.
dividend
- The number to be divided to find the remainder.divisor
- The number to divide by.
=MOD(10, 7) -> 3
=MOD(-10, 7) -> 4
=MOD(10, -7) -> -4
=MOD(-10, -7) -> -3
=MOD($field, 2.5)
=MOD(DECIMAL($integer_field), $decimal_field)
MOD(integer, integer) -> integer
MOD(decimal, decimal) -> decimal
-
Any field for which
ISBLANK
returns true will be treated as0
-
Since
MOD
performs a division, a divide by zero error will result if thedivisor
is0
-
There's some contention mathematically around what value should be returned in the event that the
dividend
ordivisor
is negative. The value returned in the case of formulas will have the same sign as thedivisor
, the same behavior as Excel. -
It is unfortunately not possible to subtract an integer and decimal fields together without a manual casting the integer field using the
DECIMAL
function. The suggested solution to this issue is incredibly complex, and your understanding is appreciated. -
Literals are auto-casted, which means they might unexpectedly be rounded. For example
=MOD($field, 2.5)
is evaluated as=MOD($field, 3)
iffield
's type isinteger
. This does not apply to formulas used as validations. -
Formulas used as validations use floating-point representation for all numbers. Although quite technical, it is recommended to read and understand the limitations and problems with this representation.
Returns the product of two numbers. Equivalent to the *
operator.
multiplicand
- The number to multiply.multiplier
- The number to multiply by.
=MULTIPLY(2, 3) -> 6
=MULTIPLY($field, 2.5)
=MULTIPLY(DECIMAL($integer_field), $decimal_field)
MULTIPLY(integer, integer) -> integer
MULTIPLY(decimal, decimal) -> decimal
-
Any field for which
ISBLANK
returns true will be treated as0
-
It is unfortunately not possible to subtract an integer and decimal fields together without a manual casting the integer field using the
DECIMAL
function. The suggested solution to this issue is incredibly complex, and your understanding is appreciated. -
Literals are auto-casted, which means they might unexpectedly be rounded. For example
=MULTIPLY($field, 2.5)
is evaluated as=MULTIPLY($field, 3)
iffield
's type isinteger
. This does not apply to formulas used as validations. -
Formulas used as validations use floating-point representation for all numbers. Although quite technical, it is recommended to read and understand the limitations and problems with this representation.
Alias of the POWER
function
Returns a number raised to a power.
base
- The number to raise to theexponent
power.exponent
- The exponent to raisebase
to.
=POWER(2, 3) -> 8
=POWER($field, 2.5)
=POWER(DECIMAL($integer_field), $decimal_field)
POWER(integer, integer) -> integer
POWER(decimal, decimal) -> decimal
- Not supported outside of formulas used for validations
Returns a number with the sign reversed.
value
- The number to have its sign reversed. Equivalently, the number to multiply by-1
. Equivalent to the unary-
operator.
=UMINUS(0) -> 0
=UMINUS(10) -> -10
=UMINUS(-10) -> 10
UMINUS(integer) -> integer
UMINUS(decimal) -> decimal
- It's usually much clearer to use the unary
-
operator:=UMINUS($field)
->=-$field
- Although extremely confusing, it can be used in conjunction with the binary
-
operator:=5 - -$field
. It would be better to change this to=5 + $field
, though, as they're equivalent.
Returns a specified number, unchanged.
value
- The number to return.
=UPLUS(0) -> 0
=UPLUS(10) -> 10
=UPLUS(-10) -> -10
UPLUS(integer) -> integer
UPLUS(decimal) -> decimal
- Shouldn't ever be needed. Exists for parity with Google sheets, and a couple other technical implementation details specific to formulas.
Returns the concatenation of two values. Equivalent to the &
operator, or template strings. Because CONCAT
only takes two arguments, it's highly recommended to use template strings instead.
value1
- The value to which value2 will be appended.value2
- The value to append to value1.
=CONCAT("Hello ", "World") -> "Hello World"
=CONCAT("Hello ", $name)
CONCAT(string, string) -> string
-
Non-string values must be converted using the
TEXT
function before being used inCONCAT
:=CONCAT("The number is: ", TEXT(5))
-
Any field for which
ISBLANK
returnsTRUE
will be treated as the empty string,""
Converts the value
to a string
value
- the value to convert to a string
=TEXT(5) -> "5"
=TEXT($field)
=TEXT($field = 2)
TEXT(id) -> string
TEXT(date) -> string
TEXT(boolean) -> string
TEXT(decimal) -> string
TEXT(integer) -> string
TEXT(dropdown) -> string
TEXT(string) -> string
-
Dates will be converted to
YYYY-MM-DD
form, using the timezone set in the user preferences configuration of the Lanetix UI. This may cause the date to be displayed differently that the date field itself, which is formatted in the UI using the timezone reported by the browser. If these timezones are different, you may see odd behavior. -
Integers or decimals for which
ISBLANK
returns true will be converted to"0"
-
Booleans for which
ISBLANK
returns true will be converted to"false"
-
The
id
type is not a picker, as is the common technical nomenclature in lanetix proper, but a more specific, formula only type that only$lanetix.id
values can inhabit