In Cloud Look-up tables you can't use Rules to insert null values for the following data types (and possibly others?):

• Date/Time
• Numeric
• Integer

You either have to use a default value (like a default date/time, or a '0'), or change your data type to text - and both workarounds have knock-on implications for things like reporting or rules and workflows used later on.

This is especially important now that we are using the OData Look-up Table API for things like Power BI. Using a text data-type for things like dates causes at the very least lots of additional formatting and data manipulation at the Power BI end.

Further, there are times when it is important for the data to have a Null value, because that represents something for workflow or process conditions (i.e. that no follow-up to a process has been planned; that no GST/tax is present for an invoice etc etc, and it needs to be blank instead of a '0.00').

It also means that some workflow calculations need further workarounds (e.g. adding days or hours to date values that are seen as 'text' can be problematic).

Is there actually a way to 'Allow Nulls' like there would be in a SQL DB?

If not - could we please add this as functionality.