So I have a summit registration form that is built into my Knack application, where users first log in and submit the main form then there are supplemental forms they complete one after the other. I cannot figure out how to create a page rule that would then hide the top menu outlined in red because not all aspects of the main form and its sub-parts (Travel details and Lodging Details) are applicable to everyone that would be submitting the form. Basically the General Form, Travel Details, and Lodging Details all come from the same table/connection called “Summit Registrations.” Because there is a known bug that Knack has referred to their engineers, I basically created sections of it into their own forms so that the rules would work as expected for what to display versus not based on selections.
I feel like I need some field that would make sense to then populate into the page rule that would make the top menu disappear." Its not a big deal if this is not possible and it has to stay there I just wanted to aesthetically get rid of it when its no longer applicable to the attendee because they can only register once.
Actual screenshots of what gets filled out. Anyone that lives within 50 miles or driving would basically not complete lodging details. Anyone driving and outside of 50 miles would complete this and lodging. Anyone flying would complete both travel and lodging details.
