Single Select Return ID

[adehaan]

I have a table called vendors. Instead database have two columns vendor_name and vendor_id. I want my dropdown to Show vendor_name. When the trigger of input changes fires, I want vendor_id to be pushed to varvenid. I have tried for two days to make this work. Google, AI,University. I just cant figure it out. Help is much needed.

[danielpomeranz]

Hey @adehaan

Loading an ID from a column value is still pretty confusing in Tulip but it is possible. You will need to create a table query filtered on the vendor_name and then use a mode aggregation on the ID.

This has come up in quite a few other Community threads. The first link has a video tutorial.

Basic "Lookup" Functions Using Table Queries and Aggregations

Hi Folks, I’ve gotten a couple of questions in the last week about lookup functions in Tulip tables. While Tulip doesn’t have a built-in lookup function, there are some techniques that you can use to the same effect. This video is a quick overview by my colleague @freedman of how you can use the mode aggregation to load a record into a record placeholder by a value in a different field. [Quick Tips - Load record by another field] Here’s a follow up from an office hours sessions wh…

[Tuesday Topic] Using Mode Aggregation

This came up in Office Hours this morning with @jmlowden, @Amit, and Frank, and I thought it might be helpful to share! Frank had a use case where an operator can be working on multiple work orders at once (for example, they run out of parts on one WO and then move to a new one) but each operator will only be working on one Part number at one time. He is using a User Table to tie a Work Order number and Part number to a user when they log in. He wanted to be able to then have the Work Order num…

[adehaan]

@danielpomeranz

vendor_name

Awesome Thank you! One other mild issue. All is working . When I do the drop down single select. The dropdown will be forced to only show that dropdown. Rather Have it so the entire list…

[nicolo.lagravinese]

You can keep the full vendor list visible and still load the correct vendor_id. The supported pattern is to create a table query filtered on vendor_name, then add a mode aggregation on vendor_id and use that value in your trigger. Tulip documents how queries and aggregations work here: https://support.tulip.co/docs/table-queries-and-aggregations. Daniel’s answer in your thread also confirms this method: https://community.tulip.co/t/single-select-return-id/15869. This setup lets the dropdown show all vendor names while the trigger looks up the matching vendor_id in the background.