+1 for me too! This would be a very interesting feature to implement.
+1 this feature seems necessary.
Airtable folks, please post a workaround here if there is one available. Thanks!
+1 pretty please!! I have the same problem and I can’t find a workaround.
+1. This seems like one of those low effort/high delight features. Seems like an easy win for the product team. Let’s keep this thread fresh!
+1 for me as well! I’ve had multiple use cases where this comes up. Thanks!
I know I posted in this topic before, but I keep running into this annoying problem. Structuring my research database would be so much easier if it wasn’t for this issue. Why would you ever want to have duplicates in a lookup field?
I agree that the Airtable engineers dropped the ball with this one, and sadly, they seem to be unresponsive to user feedback like the comments in this thread.
There is one partial workaround to this dilemma, but it doesn’t provide the full functionality of lookup fields (which have now become clickable items in Airtable):
Would be great to have this feature.
Adam from the Airtable customer support team here. I had an Airtable user reach out with a link to this community post. While I can’t speak to a specific timeframe for when this feature might be available I have a workaround that may help.
I used the Recipe, Ingredients, and food type example from earlier in the thread. Also, you will need to have some comfort with our Automations feature in order to use this method:
Hope this helps and know that our team is very thankful to our community!
P.S. It may make more sense to set up the automation trigger to be “When a record is updated” and have it just watch the “Array Unique” rollup field.
Although it doesn’t resolve the underlying issue, I found this to be very useful.
Thanks for posting!