Retrieving “unspecified fields in document” error when trying to insert a document

Hello,

Since today we encounter a strange issue regarding an insertOne into the MongoDB Atlas backend. We have adjusted nothing, no changes to rules, schema or functions but suddenly the inserts are failing.

The wild thing is that the error is not even consistent:

role “Customer” in “main.customerOrder” does not have insert permission for document with _id: ObjectID(“67e2c57fcaa0801c71a09ce2”): terms: unspecified fields in document: [paymentTermConditions note paymentTerms deliveryTerms]

role “Customer” in “main.customerOrder” does not have insert permission for document with _id: ObjectID(“67e2c577caa0801c71a09ce0”): destination: unspecified fields in document: [_id name street city contactPerson houseNo type postalCode country]`

role “Customer” in “main.customerOrder” does not have insert permission for document with _id: ObjectID(“67e2c886caa0801c71a09ce4”): contractInformation: unspecified fields in document: [contractNo _id]

The field that errors that randomly changes. Since we could not find any changes on our side we are afraid that Mongo itself changed something that led to this issues?

Hi!
We are not using device sync.
We are using the insertOne function of the realm-web npm package inside a React Application.

There is nothing missing inside the schema. The exact fields that are mentioned inside the logs are there AND got the correct type. The exact same calls worked yesterday, nothing was changed on our side. We are just suddenly receiving errors.

Okay, I understand. But this “unspecified fields in document” error is completely new.
When googling you find 0 matches. I feels like there was something new introduced here that destroys functional code.

Like the change some weeks ago where suddenly github deploys of applications with config.json that contained a function name multiple times were no longer working.

Okay I understand…

Just as an update - I adjusted the worflow to perform the insert one inside a function that is run as system.

The insert was successful and the inserted document is valid to the schema. So we will use this as a workaround now.