Discussions

Expand all | Collapse all

Restricting other app lookup fields

  • 1.  Restricting other app lookup fields

    Posted 02-04-2020 12:53
    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
    ------------------------------


  • 2.  RE: Restricting other app lookup fields

    Posted 02-04-2020 15:18
    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
    ------------------------------



  • 3.  RE: Restricting other app lookup fields

    Posted 02-05-2020 10:32
    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
    ------------------------------



  • 4.  RE: Restricting other app lookup fields

    Posted 02-05-2020 14:21
    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
    ------------------------------



  • 5.  RE: Restricting other app lookup fields

    Posted 02-06-2020 09:25
    Drew,

    I strongly suggest removing the multi select fields from the application.  Put in a new table and drive everything with a relationship.

    The multi select is a bit faster to start the app building process.  However you will run into issues later as your workflows get more sophisticated.  It is also a huge deal in reports.  If you change the spelling or correct a multi select in anyway all your reports are broken.  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 Larson
    Paasporter
    Westlake OH
    ------------------------------



  • 6.  RE: Restricting other app lookup fields

    Posted 02-10-2020 15:18

    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
    ------------------------------



  • 7.  RE: Restricting other app lookup fields

    Posted 02-10-2020 15:38
    Edited by Don Larson 02-10-2020 16:32
    Drew,

    How many multiselect fields do you have in a single table?  That will limit how many you can associate with the record.   Another way to do this and have unlimited amounts of associated items is to make a many to many between the Ticket and the Types.  Here is a picture:


    When your users add a record to Ticket Modules  the CDD that @Mark Shnier (YQC) described will limit them to Modules that have the same Ticket Type as the Ticket.

    You can have as many Ticket Module records as they want to add.

    This describes having many Modules but would not address the Tags that belong to Modules.   Do I have the first business case correct or will you have one Ticket Type, then only one Module followed by many Tags?





    ------------------------------
    Don Larson
    Paasporter
    Westlake OH
    ------------------------------