Notifications
Clear all
Topic starter
Hi.
I've encountered an issue with the Airtable node when my Airtable tables include a field named ‘id’.
Issue:
When creating or updating a record in Airtable, if the input data (fields) contains a property named ‘id’, its data is not being reflected in Airtable.
After reviewing the code for the Airtable node, I found the following:
The command on line 502 appears to assume that a field named ‘id’ should never exist, which is not always the case. (I understand that Airtable records have a built-in ‘id’ property, but this shouldn't prevent a custom ‘id’ property within the fields if that's what's intended here.)
Many of my Airtable bases have tables (often several at once) with fields named ‘id’.
Could you please provide some guidance on this?
Thanks.
Posted : 16/07/2021 12:15 pm
Ah yes, that makes sense. Modifying that would unfortunately be a breaking change. For the time being, could you please rename "id" to "Id" or "ID"?
We can address this once node versioning is implemented and we update the Airtable node.
Posted : 16/07/2021 3:22 pm
Topic starter
I was planning to implement that for the time being. However, my current workflow involves importing data from external sources and then synchronizing that data as is. The incoming data contains nested properties defined as ‘id’. Mapping all of them would necessitate adding some temporary, additional logic, which I'm trying to bypass.
If the Airtable node update occurs within the next few days, I will simply wait for it; otherwise, I will implement the temporary logic for now.
Posted : 16/07/2021 3:28 pm
Uh no, apologies. We don't actually anticipate that occurring for at least another 1-2 months.
Posted : 16/07/2021 3:40 pm
Topic starter
Alright, I will use a workaround for now.
Posted : 17/07/2021 3:03 am