You are here:
How Null Values Are Handled in Expression Sets
You can make sure that null values or preconfigured default values in decision tables are preserved during calculations in expression sets based on your business requirements.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions for clouds that have Business Rules Engine enabled |
When you create an expression set, you can initialize resources with null or default values.
-
To initialize the expression set version resources with null values, turn off the Initialize resources to default values option when you create an expression set. To customize how null values are handled, use the IsNull and IsNotNull operators and functions in the condition, list filter, and calculation steps.
-
To initialize the expression set version resources with default values, turn on the Initialize resources to default values option.
If you use the lookup table element as a step in an expression set version, the input and output variables from the table are imported as local resources of the expression set version.
| Initialize Resources to Default Values | Decision Table Output | Default Value | Expression Set Output | Comment |
|---|---|---|---|---|
| On | Null | 100 (value set by user) | 100 | The default value overwrites the Null value from the decision table if Initialize resources to default values is on. |
| On | Null | none | 0 (internal default value) | NA |
| Off | Null | - | Null | The Null value from the decision table is preserved if Initialize resources to default values is off. |
| On/Off | 10 (Any non-null value) | - | 10 | The non-null value from the decision table is set as the expression set output. |
