Error message when try adding a linked record

Hi @Paintedhouzz_LL,

Hmm somehow Airtable thinks you don't have permission to edit the linked table as selecting linked records updates values in both tables. Have you tried replicating the error in the browser app? That might rule out if it's a bug in the iOS app.

-Stephen

It works fine on Mac Safari browser.  

Ah could be a bug 😞 You might try contacting Airtable support to assist here

https://support.airtable.com/docs/contacting-airtable-support?contact_support=true

@Juliana11 

Thank you! I just did. Let´s see…

Thanks for alerting me of this @Stephen_Orr1, and thank you @Paintedhouzz_LL for surfacing this behavior—it definitely sounds odd to me as well! If it were consistently producing this error I'd think that table editing permissions were at play, though due to the immediacy of the error after selecting the linked record field and isolation to iOS apps, it sounds like something else may be going on. I see that one of my colleagues is currently on the support ticket, so we should hopefully have the cause pinpointed shortly. Thanks again for your assistance during this process!

I have been having the same issue.

I am having the exact same issue. Only on iOS app version v9.4 (8475). 

To troubleshoot: I created multiple linked tables to test other linked fields. That went without any issue. Only this one specific table (not synced) is showing the popup. 

Same issue here.  Multiple accounts, multiple iPads, permission levels, etc... there's just one linked field that seems to be cursed.  I even tried duplicating the field, re-linking all the dependencies, and it still gives an error.  It's definitely not an issue with permissions since the error only occurs on the iOS app on the iPad and it specifically prevents me from adding linked records.  If a linked record exists, I can delete it.  

Anecdotally, it seems to work on my iPhone -- but the issue seems to be inconsistent so I don't know if that's a reliable signal.

Has there been any update to this? We have interfaces setup for employees also not having full Base access with iPhones that are having to select a specific record, and are unable to. Like others also, they can select other records in other interface pages, however of course, the specific page we need them to utilize, isn't working.

Having this same issue, started completely out of nowhere.  One day working on iPad and iPhone, the next day working on neither.

Stephen, this gave me the right path towards finding a solution in my case, the part about "updates values in both tables". Thank you.

I tried really getting to the bottom of why this was happening with some tables and not others, so I duplicated the table I wanted to lookup records in and removed all fields except for the primary field. 

Let's call the "parent" table, the Table whose record I want to link, Table 1, and the Table I want to link it to (the Table I'm in when trying to add a record and link the Table 1 record to it), Table 2.  Let's call my duplicated Table 1, Table 1 Copy.

Linking a record from Table 1 Copy (which has only the primary field) worked fine.

Then I added lookup fields to Table 1 Copy for the first 6 or so Table 1 fields (the ones that appear when selecting a record on the iPad) to Table 1 Copy - ok, error. 

Then I removed an Attachments Lookup field, which was finding photos I would add to the records in Table 2 which would appear in Table 1 through a lookup field.  Works fine.

So, the solution was just a question of re-ordering the columns that appear first, and thus which fields appear in the little pop-up box that shows you those fields when you go to link a record from iPad.

For those who don't know, Airtable will show you the Linked Record columns in the order they are set in the first (top-most) view of the Linked Table, unless you choose to allow a record selection from a specific View, in which case that View's column order is followed, and those values are shown in the selection box for the linked record.

If this works for someone else too and they would like to mark this issue solved, that'd be great.