Forum Discussion

DouglasFolk's avatar
DouglasFolk
Qrew Cadet
6 years ago

Dynamic form rules don't work correctly



The Otherwise - supposedly lets me know what's going to happen. But it doesn't work.
When I preview - and make changes to the field that is driving this is a radio-button - the actions don't work as shown.
  • Not a lot we can do to help, here, unless you can post more info about your scenario. It might be best to open a support case so a QB tech can have a peek.
  • No Pink Warnings. 

    What I want to do is turn off fields when a selection in the field "Action-Reply" = None(Specify).
    Notice the "Otherwise" - it is completely backwards.

    When Field "Action-Reply" = None(Specify) I want to see the field "Action-Specify". 

    When in the form - it does the opposite. 

  • The hide show is just stupid.
    If I hide them with one action and show with another they conflict. The only way around this is to create a dummy field that would control what shows based on the content.

  • You sometimes need to adjust your thinking to avoid form rule conflicts.

    Consider just that single field which is dependent on two situations in your mind.  Take that field out of your existing form rules and make a separate form rule to just deal with that one field.

    Ask yourself to state clearly when you want that field to show and make a rule to do what you say.
  • That's what I've been trying to do this morning.

    F1 Drives hide/show for F2, F3, F4, F5

    Lets Say F1 = X, Y, Z

    Scenario #1 
    F1 = X
    HIDE - F3, F4, F5

    Scenario #2
    F1 = Y
    HIDE F2, F5

    Scenario #3
    HIDE F2, F3, F4 

    I thought about setting a dummy field to say 1 and hide F2,F3,F4,F5 when new document.

    But will still have conflict when turning the fields back on because of hiding. Multiple Rules for same field.

    Help me think outside the box on this, please... Really I am open to suggestions



  • Ok,

    Clear your head. Disable or delete your current form rules involving these fields.


    Hands off keyboard.


    Take out a piece of paper. Seriously. Pick up a pen. Write down a single sentence when Field 1 should show.


    Put down pen.


    Hands on keyboard. Write form rule to do what you said.


    Hands off key board.


    Pick up pen. Write down in a clear sentence when Field 2 should show. Put down pen.


    Create form rule 2.


    Repeat.


    You see, you have to stop being fixated on your scenarios and instead translate them into a specific rule for each field(s) or section which needs to behave similarly. Write the rule from the field's perspective and not the perspective of your mental scenarios. If there are groups of fields that will behave identically you can put them in a section together and do the form rule in the section.
    • AlexCertificati's avatar
      AlexCertificati
      Qrew Cadet
      Of all the kinds of good advice you give on this forum, Mark, I think this one is my favorite.
    • DouglasFolk's avatar
      DouglasFolk
      Qrew Cadet
      I like the approach and that is exactly what I did. I broke into scenarios. Rules is what I should have called them. There are three selections in this field and would require three hide rules. 
      I will re-read your post and try again.
  • AustinK's avatar
    AustinK
    Qrew Commander
    Depending what the field is it may be able to be on the form in several spots without issue. If that is the case(it is colored blue in the form builder when trying to select it a second time) then I would try doing this with sections. Show and hide sections based on the drop down and have everything you need in those sections, sometimes duplicating fields. You should have no conflicts with that.