Update does not accept return_fields_by_field_id parameter about pyairtable

[marks]

Hi @NicoHood & @mesozoic - the Airtable PATCH/PUT endpoints for a single record now support returnFieldsByFieldId

[mesozoic]

Thanks for resolving this issue, @marks!

[mesozoic]

That's true! Unfortunately this is a limitation of the Airtable API; passing returnFieldsByFieldId to the update endpoint returns a 422 (unlike the batch update endpoint, which does the right thing).

In the branch you mentioned, there's a commented-out test showing how we could test it, if it were supported.

[NicoHood]

WTF? Alright, wouldnt it make sense to use the batch api then? I mean we could keep the same syntax and whenever airtable fixes this issue we could switch the call internally? That would make more sense, as we do not need to work around in the user code. Or is there any advantage in the "normal", single update call?

[NicoHood]

Nice! So then we could just enable it, right?

[mesozoic]

I'll reopen the issue. Pull requests are welcome!

[NicoHood]

I am sorry I aint got time to work on this. I know the fix is easy, but I have other priorities. Would be nice if someone else could add this parameter :-)

[marks]

@NicoHood - I believe PR #320 takes care of this for you if you want to go over and subscribe for updates over there