Field selections based on other fields
Hi, I am trying to create a sort of workflow for people creating a case. Essentially, I want them to: 1. Choose a department. 2. Then choose a level based on the chosen department. 3. Then choos...
Forum Discussion
Hi, yes it makes sense.
In order to do this you will have to do Conditional Dropdowns in order to select the following filed based on the first one.
Here you have a link that might help you with this.
https://helpv2.quickbase.com/hc/en-us/articles/4570365398036-Conditional-dropdowns
good luck!
------------------------------
Francisco Ojeda
------------------------------
To add some color to Franciscos comment - you'll want to use conditional dropdowns but first you'll need to make tables to house your departments / levels / roles / positions.
Your departments would just be a list of departments, your levels would be your list but each one would be related via a new relationship to departments. Roles would then be related to levels, and positions related to Roles. This then allows you to create the conditional dropdown flow you're describing.
------------------------------
Chayce Duncan
------------------------------Thank You Both! I'm going to give that a try!
------------------------------
Renee Hansen
------------------------------I actually need to add a 4th layer to this.
I have a connected table to all of the positions. I want the Positions narrowed down to what is available, based on the other choices they've made in Department, then Role, then Level.
I'm not sure how I need to arrange those relationships.
They'll be entering this on a "Main Table" or "project table"
in that table they'll enter all the details and then start the selections. The objective the entire time is to find a position that matches the criteria (dept, role, level = positions available).
------------------------------
Renee Hansen
------------------------------Just to confirm - the Positions are being synced as a connected table? Do you control that source information or are you just receiving it as is and can't make any updates to it?
The general setup should still be the same though - your relationship structure would be:
Departments have many roles
Roles have many levels
Levels have many positions.
The key is that you'll need to someone marry that 'Position' back to the correct level. Th ideal scenario would be that you can actually relate levels and positions directly via a true relationship/field that you can enter data into - however, you can also make you're conditional dropdown based on a string instead. So in this example you have something like:
Department = Finance
Role = Director
Level = 2
In your positions table if you had all 3 fields present - you could make a string like
Finance - Director - 2, and then in your 'Projects' table, make that same string combination based on the user entry, and then make your conditional dropdown based on those fields matching. In this way - you don't need a direct relationship to tie them together - you're just combining strings to see what matches in your positions table.
------------------------------
Chayce Duncan
------------------------------
