Skip to main content
Question

Limit Record Selection & Other Basic Tasks AT cannot do....

  • September 28, 2026
  • 5 replies
  • 23 views

Jasmine_Ruth1
Forum|alt.badge.img+9

There are many many frustrations since we’ve upgraded our Airtable, there are seemingly low level tasks that Airtable and Omni is unable to do, yet it boasts being able to build an entire base. Extremely annoying. I just wanted to list a few here.

  • Why can we restrict record selection on an interface for clients on a linked file but not on a single or multiple selection?
  • Why can’t we put a prompt into Omni to hide or show columns? This is very helpful if we need to add a same view to other like bases but it’s not able to hide or show columns? 
  • Why can’t we copy an interface and then change where the linked data is coming from? This is a HUGE problem that was misrepresented by Airtable. We thought we could make a linked base, and link the views so that all our clients could use this linked base. Only to find out I’d have to manually set up each interface one by one, over and over again because Omni does not work, and the option to change where the data is pulled form is greyed out
  • PORTAL users used to be able to @ tag other users, and Airtable took this away. This is not coming back and this means basically airtable forces all portal clients to now be collaborators at of course a premium cost. Just noting this here as an annoyance so other users know because it took months of me working with their tech support for them to admit this was a change that happened sometime in the last few months. 

 

5 replies

CaitlenBerg
Forum|alt.badge.img+8
  • Inspiring
  • September 28, 2026

I’m not sure about the rest of your points, but for the first issue regarding restricting a selection, can you explain a little more about what you’re looking to do? I think this should be possible, unless I’m misunderstanding your requirement.


Jasmine_Ruth1
Forum|alt.badge.img+9
  • Author
  • Known Participant
  • September 28, 2026

I’m not sure about the rest of your points, but for the first issue regarding restricting a selection, can you explain a little more about what you’re looking to do? I think this should be possible, unless I’m misunderstanding your requirement.

The “Limit Record Selection” is only available when it is a “linked” record. See below:

However for a single or multiple select, the “limit record selection” is not an option, so I cannot restrict which options an interface user can use. 

 


CaitlenBerg
Forum|alt.badge.img+8
  • Inspiring
  • September 28, 2026

This looks like a screenshot from the data layer of the base, but you mentioned that your clients are working from an interface, is that correct?


Jasmine_Ruth1
Forum|alt.badge.img+9
  • Author
  • Known Participant
  • September 28, 2026

This looks like a screenshot from the data layer of the base, but you mentioned that your clients are working from an interface, is that correct?

Yes the screen shot is to show how there is an option for “Limit Record Selection” on the linked file, but not on the single select file. No need to show client view in this case. This view is what sets up the interface. Based on how I set this up on the back end is what the client sees. The client is restricted to selecting only the options I allow for a LINKED record, but I can’t do anything to restrict on a single or multiple select. As you can see from the screenshot the “Limit Record Selection” simply is not there on the single/multi select.


CaitlenBerg
Forum|alt.badge.img+8
  • Inspiring
  • September 28, 2026

​@Jasmine_Ruth1 I checked a base of mine where I’ve restricted available selections and I could’ve sworn that it was a field native to that table, but I was wrong - it’s a linked field. I don’t know why that makes a difference to Airtable. I’m assuming you’re not able to change that field to a linked field.
Sorry I couldn’t be more helpful.