Yes, I definitely read
Note that any field not included in the PUT request will be deleted, included built in fields such as ‘Created Date’, so use with caution
as saying that you need to make sure to include the built in fields otherwise they will be deleted.
And not seeing any specific language in either the modify or replace section indicating that the built in fields can not be modified or replaced, I naturally assumed they could be.
When I first tested this back in 2020 the only built in field not working was the created date, so my first attempt resulted in all fields filled in (modified and created by) but not the created date. I reached out to support back then to find out what was the proper syntax, either Created Date or Creation Date since Bubble uses both interchangeably in the system and never got an answer on that, nor was I informed it not possible or possible to make changes to the built in fields via the API.
Now when I am testing again with this setup below
I get this result in the database
The use of the query string checkbox makes it so the initialization doesn’t report any errors and shows the 204 success with empty body as per the documentation, but clearly the custom fields are empty, but the built in fields are not empty and the Modified Date is the current date and time. So the values sent are ignored, but still the entry is modified.
Then when I remove the query string parameter and the built in fields as below
I get the following result in the database.
The values I sent for custom fields are correct, however, the built in fields are not deleted as the documentation says they will be.
When I uncheck querystring from the first setup with the built in field parameters still present, I get the error of unrecognized field for all 3 built in fields.
So, clearly I’m very confused on what is what. Still waiting for support to respond to my request for more clarity on the subject.