Inconsistent behaviour of null values

Inconsistent behaviour of null values

ZC Team:

it is a really good things that recently you made possible to update fields with null values. But I think that there is an inconsistency in handing null values

1. If I have for example a field, it is allowed to allow null values there

Numeric_Field = 1;
Numeric_Field = null;

But if I have a numeric varialble, the following statements

Numeric_Var = 1;
Numeric_Var = null;

will generate error:
The template variable Numeric_Var is of type BIGINT. But you are trying to update it with an expression of type NULLTYPE

2. The functions can't return null values - so it is not possible to update fields with null values using functions other than void type. If a function returns null, this is seen as an error and the entire script is blocked, even if it would work ok to update a field with a null returned value.

I think that a step further is to allow variables to be updated with null values and functions to return null values without errors.





Regards,
George