add is null and is not null as property relation options

[sarahcd]

I don't have a specific use case, but 'is null' and 'is not null' could add more possibilities for using this app.

[andreakoelzsch]

not sure what you mean with this, lets discuss tomorrow

[andreakoelzsch]

mortality column or else which can be empty or have entries/an entry. meant "all(is.na)" or not

[annescharf]

I'm going to update this App in the next days. @sarahcd do you remember what lead you to post this issue? From what is written here, I'm not quite sure how to implement it. Thanks!

[sarahcd]

I saw it as an option in addition to the current choices ( = > < ) that might be straightforward to implement. I probably thought of it, generically, because I use is.na and !is.na a lot for the duplicate filter. Following Andrea's comment above,

• Say a status field contains values "error", "missed fix", or is blank if everything is ok. In this case you might want to get an alert if the field is not blank.
• Similarly, if the status field contains "error", "missed fix", or "ok", you might want to get an alert if it is anything but "ok".
  Again I don't have a specific use case, so we can also just leave the ticket to see if anyone puts in an actual request for it.

[annescharf]

Thanks @sarahcd, ok, I get the idea. Yes, I would leave this issue open, and if someone has a specific request, we can implement it. It is easier to work with a concrete situation than trying to make one up.