I'm working on a form with some fairly complicated logic rules, and I keep running into an issue where a field - that should be hidden due to logic rules - is showing up by default despite user form selections.
Basically, this form allows users to create work requests based primarily on a field where they choose a request type or types (multi-select dropdown list). Here's the default view for the form:
These submissions all need to also choose a location where the work will take place, and depending on the request type, there are different ways to record that location.
The most common method for recording location is a text/number field where users can enter a Location ID. For certain request types, that is the only way to record a location. In other cases, I've provided a checkbox for "I don't know the Location ID", which when checked pulls up a dropdown list of locations and removes the Location ID field. Here's that logic:
Now this all works perfectly well and good when all my logic rules that contain this field are part of that first "Request Type" dropdown menu. However, I run into my issue when I try to put that "I Don't Know the Location ID" checkbox in the logic of a field that's subordinate to the original "Request Type" field. Here's what happens:
For one of my Request Types, there is logic to bring up a field called "Location Type". If I create a logic rule for a Location Type selection that brings up the "I Don't Know the Location ID" checkbox, the form logic breaks and the "Location ID" field is now visible by default:
The most annoying thing here is that if I change the vertical order of form elements in the form editing - that is, by moving the "Location Type" field above the "Request Type" field, it fixes the issue and the "Location ID" field behaves as expected. But now I've got users having to fill out the form from bottom up, and I'm certain that will cause human errors.
Anyone know how to work around this?
