Forum Discussion

ChuckHardy's avatar
ChuckHardy
Qrew Trainee
4 days ago
Solved

Dynamic form rule inconsistency- (display message on open)

Hi -- I'm trying to create what I thought would be a simple rule to display a message when a record is opened, if a field is set to a certain value.  I can't get the rule to work, but as I have been troubleshooting, I have found certain field types work and others don't.  So far, I see that checkbox fields seem to work,  but formula-based checkboxes and multiple choice text fields don't.   Can someone explain why this is, and if there is a work-around?  I would like my message to be based on the a formula-based checkbox being checked.

Forms
  • Laura_Thacker's avatar
    Laura_Thacker
    4 days ago

    No, there's no "conversion" for legacy forms to move to new forms; you have to rebuild.

    Make sure your Rule is at the top is my next-best suggestion; I've had rules not working in the past and then by moving them; I see magic happen.

    Also submit a Support Ticket if moving the Rule does not work - verify this is a bug (or intended behavior).

7 Replies

Sort By
  • MarkShnier__You's avatar
    MarkShnier__You
    Icon for Qrew Legend rankQrew Legend
    4 days ago

    Form rules on Legacy forms (less sure about New Forms) typically do not work on fields which are not on the form. Especially if they may change based on data entry fields changing on the form. So the first thing to do is put those formula fields on the form. If that solves the problem, then just put them in a section on the forum called "Required for form rules" and then make a rule that will cause that section to always be hidden.  As long as it's on the form the form will see the fields, even if hidden.

    • ChuckHardy's avatar
      ChuckHardy
      Qrew Trainee
      4 days ago

      Thanks Mark,  I've been bitten by that one before and have indeed included those field s on the form so that's not it.   I like your solution for not cluttering up the form by adding the new section.  I'll file that one away for future.

  • Laura_Thacker's avatar
    Laura_Thacker
    Qrew Captain
    4 days ago

    Are you using new-style forms or legacy forms?  Can you replicate this behavior in different browsers?  Have you tested your rule in both NS and LS forms?  Is there a difference?  Please submit a support ticket if this is cross-browser and different behavior in New Style forms v. Legacy forms.  

    If this is a critical behavior, consider using the form style that it works in until there is another fix.  Also; consider a formula-field for the message if it should be displayed on the screen rather than as a "pop up" type message for example.  Formula-fields relying on Formula-fields to output a value should work regardless of the Form Style your users are using.

    • ChuckHardy's avatar
      ChuckHardy
      Qrew Trainee
      4 days ago

      Thanks for the fast reply. 

      This is a Legacy form.  It is an existing form that I am adding functionality to, so it was not created via the new format.  Last I checked, there was not a conversion feature for existing forms.  Is that still the case?

      I'll try out the idea of the formula field, but I do like the "in your face" aspect of the pop-up message in this case.

       

      • Laura_Thacker's avatar
        Laura_Thacker
        Qrew Captain
        4 days ago

        No, there's no "conversion" for legacy forms to move to new forms; you have to rebuild.

        Make sure your Rule is at the top is my next-best suggestion; I've had rules not working in the past and then by moving them; I see magic happen.

        Also submit a Support Ticket if moving the Rule does not work - verify this is a bug (or intended behavior).

  • ChuckHardy's avatar
    ChuckHardy
    Qrew Trainee
    3 days ago

    Thanks -- moving it to the top worked.  Why?  I have no idea, since the rule based on only the checkbox worked at the original position.  Thanks for the answer!

    • Laura_Thacker's avatar
      Laura_Thacker
      Qrew Captain
      3 days ago

      Chuck - I do not have an easy answer.  Here's a Quickbase link for future reference: https://helpv2.quickbase.com/hc/en-us/articles/16148473308692-Troubleshooting-form-rules

      I am sure it has something to do with how sequentially Quickbase reads the Rules and how they are setup.  Moving Rules around generally should resolve problems like this since they should all be independent of each other and non-conflicting.  If they conflict only the highest-number one will work (ie. the lower down the list).