Forum Discussion

joevandervest's avatar
joevandervest
Qrew Cadet
2 years ago

New Forms - Rules Test for NULL or 'unset' DATEs

Forgive me if I missed something about this elsewhere, but for the life of me, i'm manually converting some forms and running into the issue with form/dynamic rules - the BLANK tests that used to work on old forms don't seem to be working in new forms. 

Now I have a work around to create a "dummy_null_field" for data types i need to test, using the null field in a "value in field" test, but that seems a bit over the top. 

Is there some way to test fields for NULL that works in New Forms rules creation?  



------------------------------
joe vandervest
------------------------------
  • joevandervest's avatar
    joevandervest
    Qrew Cadet
    2 years ago

    I figured this out. 

    For those that might be confused: 

    Use the FORMULA BUILDER in the create/edit rules interface to create a simple test that should produce a boolean output.   e.g IsNull([something])=TRUE or Nz([something])=TRUE depending on datatype

    Then if the bool is TRUE the action you identify in the action section will happen. 




    ------------------------------
    joe vandervest
    ------------------------------

    • JoelHickok's avatar
      JoelHickok
      Qrew Cadet
      2 years ago

      While I also search out work arounds like you have done here, I still feel like this is an issue.  We should not be forced to create new fields and workarounds to do something basic that the form should be capable of doing on its own.  Especially since the old forms allowed this more easily.  

      Let's take steps forward not backwards!

    • rbuschmeyer's avatar
      rbuschmeyer
      Qrew Trainee
      2 days ago

      Joe, I have a similar issue on the "new" forms that's frustrating the hell out of me.  I have the exact formula you have listed above using IsNull:  IsNull([Related Deployment])=TRUE

      What I'm attempting to do is hide a section of the form if the related field is not set.  This formula is still not yielding the result I want.  

      Screenshot of rule attached.

  • MarkShnier__You's avatar
    MarkShnier__You
    Icon for Qrew Legend rankQrew Legend
    2 days ago

    The problem may be a mismatch between how the field [Related Deployment] is set to handle nulls and how your formula is handling nulls.  If the Field Properties is set to treat blanks as zeros then is not will not work. You would have to compare as to whether or not it is equal to zero. Or else go to the field properties and de-select the checkbox to treat blanks as now. Then you can use IsNull.