You can get the field key in the admin where you create the fields <- this is a nogo, overkilling workflow for a deployment script.
Unfortunately, my expected behavior on updating an existent POST / un-existent custom field in production, did not caused an issue and correctly created the field reference “field_5ac3e34638087”.
So I am still confused when we HAVE TO use the field for updating records.
The only scenario left I could think of, is when the field does not exist at all, and then you try to update it, then it would make sense to go and create one manually or programatically, and then update it.
Thnks for any comment you may have on this.
