The Community will be temporarily unavailable starting on Friday February 28. We’ll be back as soon as we can! To learn more, check out our Announcements blog post.
Hi Airtable community,
I am stumped with a bit of an annoying task here. We have an attachment field in our Airtable base where we attach DOCX files. We want to return this field as a part of an API response from our custom API, and we want to do a f...
Hey everyone!
Today we had an issue where a few of our automations started failing due to all of our “Link to _” fields breaking. We have been using these fields as a main link between tables, and they have all started failing with the same error:
Fi...
That is a great idea. Half of the reason for doing this as it is a “preview”, and we really don’t want the user being able to have access to the file itself, but I can mess around with the idea and see if theres a way to hide the document itself from...
I have received an email from Airtable support:
“So sorry for the inconvenience here! As it turns out there was an issue on our end with automations that use an autonumber field. Our team has let me know that they’ve fixed this, so you should be seei...
This seemingly fixed it!
Using the Airtable Record ID is working. We were originally using the autonumber type primary key in the “Link to record” fieldm, but now using the Airtable Record ID is working, and showing the primary key in the field. I be...
The new entry is set on a trigger when the table with the primary row is created.
To explain the automation:
Once an entry in table A is created, create an entry in table B with “table A ID” set to the primary key (autonumber) of table A.
The error w...
It was a “Link to Record” field. It is how multiple tables of ours communicate data to one another. It was trying to put in an “ID”, which was created as an autonumber on a separate table.