Help

Re: Remove duplicates in look up field

5332 0
cancel
Showing results for 
Search instead for 
Did you mean: 
Mathias_Elmose
7 - App Architect
7 - App Architect

I’m a big fan of look-ups but I would really like to be able to remove records the occur more than one time. Is there a way to do that?

112 Replies 112

It IS a workaround, but it’s not very scalable, as creating 3 additional fields and an automation for what is essentially a field-level filter is not a particularly elegant solution. And then good luck trying to explain that workflow to a non-experienced user. The simplest solution is to not make users think or create a Rube Goldberg machine to do something that really should be a no-brainer.

And this also goes for linked records on the same table. Please give us a simple switch to allow the linkage to apply to both records. For example, if I have a Software table and have a same-table linked record field called Integrations, if I use this field to link Airtable to Zapier, I’d want an option (at the field-level) to make this a two-way linkage so that Zapier is also linked to Airtable in this instance.

Tom_Gale
4 - Data Explorer
4 - Data Explorer

+1 really need this feature…

Maria_Robertson
5 - Automation Enthusiast
5 - Automation Enthusiast

Here to join the party, I’ve also just come across this need. Trying to organise references and research for individual animal species, but view easily overall content within their families.
Having this feature would be the final puzzle piece.

Steven_Benders
5 - Automation Enthusiast
5 - Automation Enthusiast

+1 to this feature too.

Jonathan_Slavut
4 - Data Explorer
4 - Data Explorer

+1 to the above, this is a sorely needed filter

Simon_Damborg1
4 - Data Explorer
4 - Data Explorer

+100000 to the above… been waiting for this for a loooong while.

Laure_Aimoz
4 - Data Explorer
4 - Data Explorer

+1 to this feature too.

Jayna_Fey
4 - Data Explorer
4 - Data Explorer

+1 to this feature - very much needed.

Taylor_Johnson1
4 - Data Explorer
4 - Data Explorer

+1 this would solve a lot of issues and prevent the need to use hacky workarounds that aren’t scalable

Adding my +1. This feature prevents our organization from really using this as it would be integral to a lot of the tables we would need to create. The current workaround is not feasible at scale.