Hello, I think a null value would be extremely helpful to use in a function for a formula field, as it would also expand the functionality for the if-function. The null value would be neutral and could therefore turn the if-function from an if-else-statement to a simple if-statement (so the structure would be if(bool, any, NULL)
).
I’m looking as well for this!
Using NULL values in formula fields is a great idea! Here’s a simple example showing how it enhances if-function flexibility:
IF(revenue > 1000, 'High Value', NULL)
This approach offers several benefits:
- Cleaner conditional logic
- More precise data representation
- Easier filtering and reporting
- Reduced complexity in nested conditions
The NULL value acts as a perfect neutral state when you only need to track specific conditions while leaving others undefined.
Hey @chantal @360Creators, what are your specific use cases or examples? While we see the value, we think using the functionempty
could be a workaround.
@olgatrykush you mean when_empty
right?
Haven’t gotten that to work yet.
It’s like what modbot was saying. I’ve been using this type of IF logic all the time in Airtable.
Fix
As I’ve been reviewing this discussion, I figured that you can make it work like this:
IF(field('revenue') > 1000, 'High Value','')
And if you want to do something if it has NULL/nothing/blank, then something like:
IF(field('revenue') = '', 'it is blank','it has some value')
Familarity from Airtable
It’s just that there’s this familarity from Airtable using BLANK()
IF(revenue=BLANK(),'its blank','it has something')
Which can work as well in Baserow, but it gets more difficult to read/understand later on.
IF(BLANK(field('revenue')=true,'its blank', 'it has something')
Just generally speaking, I think formulas should have the same look and feel as Airtable or Nocodb. But that’s probably quite an intense task
hey @360Creators
Yes, this one
Ronald, thank you for sharing the examples. We’ll review them and rediscuss this request to add a NULL
value.