This is another one of those frustrating aspects of Airtable that you come across sometimes. Sure it might not be “best practices” to have a table with 100+ fields, but lots of us do. And while it’s certainly possible to come up with hack-y little tr...

I’m trying to almost exactly this and struggling. I have a Zapier zap creates a new Airtable record in Table A any time there is a form submission on my Squarespace site. In Table B I use the timestamp of each record from Table A to populate a bunch ...

Likewise late to this convo but I agree that tagged fields would be extremely helpful. We have tables with many fields, for projects with several collaborators, and it would save a lot of time/headache if it were possible to create views by filtering...