# App Services Schema Validation > Depth-first rabbithole dossier for App Services Schema Validation; source-anchored research pack. Parent: [MongoDB Atlas App Services](https://llms-explorer.com/tree/mongodb-atlas-app-services/) · 2 facets · 3 facts · page: https://llms-explorer.com/tree/app-services-schema-validation/ ## 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: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/app-services-schema-validation-5d2b962eb2/rabbithole-synthesis.md#troubleshooting` ## 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: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/app-services-schema-validation-5d2b962eb2/rabbithole-synthesis.md#troubleshooting` - [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: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/app-services-schema-validation-5d2b962eb2/rabbithole-synthesis.md#troubleshooting` ## 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