Pretty sure this isn’t expected behaviour: Creating a lookup, importing rows from another table. Text fields are imported correctly, but for option fields (which I love to use to validate data instead of free text, e.g. gender (male/female)), I’m only getting the optionId. is this supposed to be like that? and if so, what’s the workaround?
This behavior is expected when using the Lookup feature. When importing option fields from another table, Clay imports the raw data values (optionIds) rather than the display values. This is similar to how object fields appear in CSV exports - they don't display the formatted values but rather the underlying data. For option/select fields specifically, Clay stores these as predefined tags with associated IDs in the background. As a workaround, you could create a formula column in your source table that converts the option IDs to their display values before using the lookup.
just wondering: am i the only one who thinks this is cumbersome and not ideal?
yes pls
Hey Daniel, thanks for reaching out! Agreed with you on this! Bumping our team to see if they're working on a better solution. The workaround here is to associated a specific ID to the value and have a formula return the correct value. I.e if the data looks like: optid = 123 = "cat" optd = 456 = "dog" Type into the formula generator: If {{optid}} equals 123, return cat, else return dog This example only uses two option id's if there are more the logic of the formula changes slightly but follows the same concept.
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.