Forum Discussion
BlakeHarrison
5 years agoQrew Captain
At present, no. Formulas cannot access data from un-related tables. How are you wanting to use this list of users? Is this just for display to the current user or is there something more that you want to accomplish?
------------------------------
Blake Harrison - DataBlender.io
Quick Base Solution Provider
------------------------------
------------------------------
Blake Harrison - DataBlender.io
Quick Base Solution Provider
------------------------------
MichaelTamoush
5 years agoQrew Captain
I'm just looking to have a dropdown list for a selection (in this case it is a selection of users, but I have this same case scenario for a simply multiple choice drop down) where the list is populated from another field, but also filtered. As far as I know you have two choices:
1. Multiple Choice Field (or other similar field) and choose to get values from another table. However, this does not allow for filtering.
2. Relate the field, and use a filtered report. This works, but I was trying to avoid creating relationships for no other reason than to get a filtered list.
3. Just thought of this - I could create another field in my source table with a formula that essentially returns the items I want, and is blank for items I dont want. I can use that as the field to get values from...
------------------------------
Mike Tamoush
------------------------------
1. Multiple Choice Field (or other similar field) and choose to get values from another table. However, this does not allow for filtering.
2. Relate the field, and use a filtered report. This works, but I was trying to avoid creating relationships for no other reason than to get a filtered list.
3. Just thought of this - I could create another field in my source table with a formula that essentially returns the items I want, and is blank for items I dont want. I can use that as the field to get values from...
------------------------------
Mike Tamoush
------------------------------
- BlakeHarrison5 years agoQrew CaptainI would encourage you to go with Option 2. While you may only find limited use for it in the beginning, you may find other ways that a 'Resources' table may be useful in the long run.
------------------------------
Blake Harrison - DataBlender.io
Quick Base Solution Provider
------------------------------