App Services Schema Validation
Parent: MongoDB Atlas App Services · Published reference · snapshot 2026-10-15 · viability 3.00 / 5 (skip)
↓ Facts as markdownall context files
Depth-first rabbithole dossier for App Services Schema Validation; source-anchored research pack.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
How it works
- [low] An Atlas App Services log message of the form 'role ... does not have update permission for document ...: could not validate document: departureLocation.geoLocation.coordinates.1: Invalid type' was reported when schema validation rejected an integer where a double was expected; the cause was the type mismatch, not a missing permission. Sources: https://github.com/realm/realm-js/issues/6219 [source]
Facts and statements
- [low] MongoDB Atlas App Services may exhibit a bug where JSON numbers are treated as integers, causing schema validation failures for fields expecting specific types. Sources: https://github.com/realm/realm-js/issues/6219 [source]
- [low] A user reported that Realm still throws exceptions for 'int' and 'double' types, which they attributed to NodeJS converting values to the smallest possible type; a MongoDB engineer instead attributed the issue to App Services treating the JSON number 1 as an integer. Sources: https://github.com/realm/realm-js/issues/6219 [source]
Related concepts
- App — is a part of App Services Schema Validation
- Services — is a part of App Services Schema Validation
- Schema — is a part of App Services Schema Validation
- Validation — is a part of App Services Schema Validation
Children
- No children recorded.