You are viewing limited content. For full access, please sign in.

Question

Question

Field Rule order of evaluation not working?

asked on January 13

I have a field that is the target of two different field rules.  One of them hides it (and other fields) when 'Yes' is not selected on a radio button, the other keeps it and another field hidden depending on what step the process is in.

Based on the documentation, whichever rule has the highest number is the dominant rule for conflicts.  In this scenario the field should be hidden whenever the radio selection is not 'Yes', and when 'Yes' is selected it should still be hidden during the specified steps.

What I'm seeing though is that as soon as I select 'Yes', the field pops up even if I'm in one of the listed steps.  I know the step rule is working because it's hiding two different fields, and the other one stays hidden.  I've tried swapping the rule order but no matter which one is above it always shows up on 'Yes'.

0 0

Replies

replied on January 13

I'm not sure what it says in the documentation, but I'm pretty sure you're not meant to have two different field rules acting on the same field. When you do that, it pops up a warning like this:

Best practice is to only have one rule per field, meaning you should probably create a third rule that contains all the conditions that apply.

The alternative would be to put that field within a hidden section, then hide the section based on the step so you don't have conflicting rules.

0 0
replied on January 13

That warning didn't pop up at all - what version of Forms is that on?

I figured I would end up having to make several specific rules to achieve the result I wanted, I was just trying to save work, though it still doesn't make sense that it behaves the same way no matter which order they're in.

Thanks for the response!

0 0
replied on January 13

Are you on self-hosted or cloud? We're on 10.4 now, but I know it's done it done that as far back as I can remember.

0 0
replied on January 13

Self hosted, 10.4.1

0 0
replied on January 13

That's odd, our test environment is 10.4.5 but our prod environment is 10.4.1 and I get a slightly different message, but I still get a warning.

0 0
replied on January 13

I wonder if it's because the conditions weren't exactly the same

0 0
replied on January 13

When I tested I used different conditions, one was looking for a non-blank text field, and other was looking for a number greater than 0.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.