Forum Discussion

JeffRogerson's avatar
JeffRogerson
Qrew Cadet
5 years ago

Quickbase IOS Mobile Executing Form Rules Improperly

The form rule I am employing hides a form section depending whether a specific field is blank or not.  Pretty standard stuff.

On a PC, the form rule is handled softly and by that I mean the as you add data to the specific field, the section does not disappear or hide until the record is saved.... exactly what I want as there are more than one field in the section to be completed.

HOWEVER,

On an IOS device (which is where most of my clients access Quickbase), the section disappears AS SOON AS THE FIELD IS POPULATED  (rule is triggered immediately by advancing to the next field, not by saving the record).....  leaving the respondent unable fill the balance of the required fields or to view what he entered, questioning whether they entered anything at all?

Anyone else experiencing this phenomenon?

Any way to make Quickbase Mobile Forms work like Quickbase PC Forms?

------------------------------
Jeff Rogerson
------------------------------
Forms
Mobile
  • MichaelTamoush's avatar
    MichaelTamoush
    Qrew Captain
    5 years ago
    I am surprised the section doesn't hide on the pc as soon as you switch out of that field. I think that behavior should be the same (though there are a number of quirks on mobile I have found).

    Will it work for you to have your rule be "When the record is saved" and "when [Field] is not blank" hide section. This way it wont fire the rule until saved.

    ------------------------------
    Mike Tamoush
    ------------------------------
    • JeffRogerson's avatar
      JeffRogerson
      Qrew Cadet
      5 years ago

      Yes, that would be ideal, but I don't believe "hide" is an option when executing a "when the record is saved" form rule. 

      Only change a field or abort the save.



      ------------------------------
      Jeff Rogerson
      ------------------------------
    • JeffRogerson's avatar
      JeffRogerson
      Qrew Cadet
      5 years ago
      Got it to work, problem was my process order was wonky, causing a form rule to fire out of order....and essentially turning off or reversing the rule that was suppose to be imposed.
      Fingers crossed.... it works properly....
      Some of us no-coders need a little more time to comprehend what we're doing I guess.
      Thanks for your note and suggestion.

      ------------------------------
      Jeff Rogerson
      ------------------------------