Discussions

 View Only
Expand all | Collapse all

Use a drop down menu instead of pop-out record picker

  • 1.  Use a drop down menu instead of pop-out record picker

    Posted 05-17-2017 14:48
    Currently, I am setting up alternate relationships between tables for filtered drop down tables. I join the two tables on record ID, then use a proxy field that is a text look up and use a report I generated instead of the standard record picker. I am getting all the entities I am looking for but they are displayed in the pop up record picker for selection, is there any way they can be in a drop down selection instead?


  • 2.  RE: Use a drop down menu instead of pop-out record picker

    Posted 05-17-2017 14:52
    Once your list gets too big QB automatically makes it a 'Record Picker', but if its still small, you can change the field properties for your 'Related XXXXX' field.  

    There is a checkbox, to 'use a record picker' rather than the standard dropdown.  Just make sure that is unchecked.


  • 3.  RE: Use a drop down menu instead of pop-out record picker

    Posted 05-17-2017 14:54
    The system will force the pop up record picker if there are more than 1,000 choices being offered to the user.  You can also intentionally (or perhaps unintentionally) force the pop up record picker by a setting on the field for Related Parent called

    "Use a record picker instead of a drop down menu


  • 4.  RE: Use a drop down menu instead of pop-out record picker

    Posted 05-17-2017 15:05
    Use a record picker instead of a drop down menu" was check off, and good to know about the over 1,000 choices forcing you to use a record picker. Thanks for the help guys!


  • 5.  RE: Use a drop down menu instead of pop-out record picker

    Posted 02-16-2018 16:38
    I am not able to find the "Use a record picker instead of a drop down menu" for the field in my app. In my case, I have a child table that has a form to select the a parent record to relate to. In the child table's field properties, this option does not appear. Am I missing something?


  • 6.  RE: Use a drop down menu instead of pop-out record picker

    Posted 02-16-2018 16:41
    As it turns out, the field in question is setup as a 'lookup' field type. I assume this restricts it from being used as a record picker? If so, is there a way to convert the field type without wrecking the relationships which have already been created?


  • 7.  RE: Use a drop down menu instead of pop-out record picker

    Posted 02-16-2018 16:50
    Are you looking at the field called something like Related Parent. For this setting?


  • 8.  RE: Use a drop down menu instead of pop-out record picker

    Posted 02-16-2018 16:57
    Hi Devin, the reference field is what controls the record picker behavior. So, to find "Use a record picker instead of a drop down menu" you can go to the field properties for the reference field within whichever relationship you're working with. On that page, you'll see it under the "Reference field options" heading.


  • 9.  RE: Use a drop down menu instead of pop-out record picker

    Posted 02-16-2018 17:46
    Success, figured it out. Thank you Brian!


  • 10.  RE: Use a drop down menu instead of pop-out record picker

    Posted 04-18-2018 21:47
    I have more than 1,000 choices (grow over time). The drop down is much faster for me. How to I force the drop down?


  • 11.  RE: Use a drop down menu instead of pop-out record picker

    Posted 04-18-2018 22:05
    Look for the field typically called Related Parent. (Whatever your Parent is called). Then edit the field properties for that fiel then there is an option to force the Record Picker.


  • 12.  RE: Use a drop down menu instead of pop-out record picker

    Posted 04-20-2018 14:34
    No. I don't want the record picker.. I want the drop down. 

    Thanks.


  • 13.  RE: Use a drop down menu instead of pop-out record picker

    Posted 04-20-2018 15:07
    A solution is this is to set up a Conditional Drop down and have the user first select a letter of the alphabet or a range of letters like A-K and L-Z.

    Then he dropdown for the choices will be less than 1,000.

    So you would have a multiple choice filter, say 26 choices form a to Z.

    The make a calculated field on the main data field to calculate that same value, ie the first letter.

    Then make the drop down be conditional on having first selected the letter of the alphabet.


  • 14.  RE: Use a drop down menu instead of pop-out record picker

    Posted 04-20-2018 15:22
    Yes but this is field for entering part numbers. All values start with a 'P'. So it is a lot faster to type 'p1001' than the name of the product.


  • 15.  RE: Use a drop down menu instead of pop-out record picker

    Posted 04-20-2018 15:28
    If they all start with P, then have the user first select from 0-9 (or P), P1, P2  etcc) and then  only show those ones, so only 10 th of the total records will be less than 1,000 records.


  • 16.  RE: Use a drop down menu instead of pop-out record picker

    Posted 04-20-2018 17:02
    I understand what you are saying about adding an extra filter field ... but people have been using this the same way for years - they are acting like I broke the app :-(


  • 17.  RE: Use a drop down menu instead of pop-out record picker

    Posted 04-20-2018 17:06
    the alternative is to filter off the report for part numbers which are inactive.


  • 18.  RE: Use a drop down menu instead of pop-out record picker

    Posted 01-31-2019 17:28
    I have a follow up question to this.  I have a list of over 1,000 (list of EE numbers) and don't want to do categories as suggested above.  Can you have the user type in their EE number instead of having the record picker or drop down?


  • 19.  RE: Use a drop down menu instead of pop-out record picker

    Posted 01-31-2019 17:51
    One solution is to allow both methods.
    You can make a data entry field called [EE number direct entry].

    Then you already probably have [Related Employee number or whatever the current relationship reference field is called.

    Then have a formula called [Employee # (final)] field like 

    IF([EE number direct entry]>0. ,[EE number direct entry], related employee number])

    Then make a 2nd relationship to the Employees table and get any lookup fields only from that 2nd relationship.