ORM: Model.save() method fails due to attempting to write to computed fields

[larsakerson]

trafficstars

The Model.save() method is failing for me when the Airtable API rejects the payload, because it includes computed fields. These computed fields are not updated locally in my code, but they are included in the model and get pushed to Airtable in the record update by default.

Is there a way to set a flag on Field classes to indicate that particular fields should not be saved directly, but instead are computed in Airtable?

[gtalarico]

This does not exist but would be probably be a good addition

[larsakerson]

I just created pull request #178 to make these updates and resolve the issue.

[fbertoia]

Blocking here also, it would be much appreciated 😀