Restricting other app lookup fields

Question

I'm not sure if I'm using the correct terms here but I'll give it my best shot:

We have an app that tracks tickets.

We have another app that tracks feature requests with two tables Modules and Tags.

Currently if you choose a ticket, you can select any combination of Modules and Tags.

We could like to change this.

We are adding an additional field to Tickets called Ticket Type.

Based on the ticket type, we would like to make restrictions to the Modules you can choose. And subsequently, when you choose a module, you can then only select specific tags.

Is there a way to limit the Modules and Tags based on a previous look up selection?

------------------------------
Drew Woods
------------------------------

markshnier__you · Answer

This is native QuickBase functionality and it works incredibly well, by that i mean that of course it works but the form is very response with no real lag time.

This is called Conditional Drop down or CDD for short. here is a link to the help text plus that link has other links https://help.quickbase.com/user-assistance/conditional_dropdowns_basic_setup.html

You would set up your master tales of the choices for the selection of Types and Modules., So 1 Type would have many Modules.

Then in your tickets table the you will have a relationship to select the Type, but then the magic is that on the field for [Related Module] you check the box that says "make this field conditional ...." and limit the choices to the where the [Related Type] selected on the Ticket matches the field in the Modules table for [Related Type]

------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------

drewwoods · Answer

Hi @Mark Shnier (YQC)I think the issue I might be having is that these are multi-select fields. Do you have any suggestions for multi-select fields?​------------------------------Drew Woods------------------------------

markshnier__you · Answer

Multi-select fields are not compatible with Conditional Dropdowns. So you may need to rethink the design of your app to decide which is more important.

------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------

donlarson · Answer

Drew,I strongly suggest removing the multi select fields from the application.&nbsp; Put in a new table and drive everything with a relationship.The multi select is a bit faster to start the app building process.&nbsp; However you will run into issues later as your workflows get more sophisticated.&nbsp; It is also a huge deal in reports.&nbsp; If you change the spelling or correct a multi select in anyway all your reports are broken.&nbsp; If you use Related Parent is equal to the record id value then you can change the table continuously and everything will work.I learned the hard way and had to remove many fields......------------------------------Don LarsonPaasporterWestlake OH------------------------------

drewwoods · Answer

We kind of need the multi selects. Sometimes a ticket isn't JUST about one module. Sometimes it can affect multiple and we need to be able to select which ones?Does anyone have any other work around for this?
Ticket type Dropdown
Dependent Module Dropdown (only displays when a certain ticket type selected)
Dependent Tag Dropdown (Only displays tags based on the previous Module selection)

This is how we are categorizing our records.------------------------------Drew Woods------------------------------

Forum Discussion

Restricting other app lookup fields

Related Content

Lookup Field not pulling Data

Lookup Field Not Pulling Data

Pipelines: Lookup newest record?

Snapshot Fields

Way to do Editable Lookup Fields?