I am working mostly with Airtable so I realized the following issues:
Update Record node:
The node also shows no editable fields, which is a problem when the node tries by default to add a value to it.
Also, the node overwrites the numerical fields by default which is a big problem.
The node doesn’t upload the documents from public URLs. Every time I want to do it, I use an HTTP node but this is not the most efficient. The same problem exists on the “Create Record node”
Find record
In the find record node when I am adding a formula with the check box field empty or false the formula doesn’t work.
Hi, tomorrow I’ll work on testing and will share the results with the developers if it turns out to be a bug. It’s true that in some cases, it can be inconvenient when certain nodes overwrite fields. I’ll check to see what we can do about this
I tested it, and it works correctly, returning all my records.
Since this is a polling trigger (meaning it runs at specific intervals on our side), it’s possible you didn’t wait long enough for it to execute. Please deploy the node and check again—it should work as expected.
Developers will check whether it is possible to identify non-editable fields so they can be excluded from the general list.
Could you please provide a screencast of the issue? In my tests, all numerical fields I created were processed correctly and were not overwritten.
The API requires a JSON object in the format url-name, but it seems to interpret the input JSON as a string rather than valid JSON. As a result, it does not update correctly. Further testing will help determine the plan for improvements.
Regarding “find record,” could you clarify? There doesn’t seem to be a similar tool in the pool of Airtable nodes.
I’ve tested this, confirmed the issues, and identified the errors. I’ll follow up shortly regarding the timelines.