The JSON specification insists on objects keys being quoted. If you change your query to {"UserID":"uid_820637"} it should work as expected. You'll need to add quotes to your object keys going forward for the JSON to be considered valid in the new NoSql explorer.
Thanks,
Liam
1 Comment
Customer Support
said
about 2 years ago
Answer
Hi Robbie,
The JSON specification insists on objects keys being quoted. If you change your query to {"UserID":"uid_820637"} it should work as expected. You'll need to add quotes to your object keys going forward for the JSON to be considered valid in the new NoSql explorer.
Robbie Graham
what am I doing wrong here? The new UI on the noSQL Explorer does not seem to like my previously OK queries.
See screen.
It's telling me - Error parsing JSON. Please use valid JSON, including double-quotes on object keys.
Hi Robbie,
The JSON specification insists on objects keys being quoted. If you change your query to {"UserID":"uid_820637"} it should work as expected. You'll need to add quotes to your object keys going forward for the JSON to be considered valid in the new NoSql explorer.
Thanks,
Liam
Customer Support
Hi Robbie,
The JSON specification insists on objects keys being quoted. If you change your query to {"UserID":"uid_820637"} it should work as expected. You'll need to add quotes to your object keys going forward for the JSON to be considered valid in the new NoSql explorer.
Thanks,
Liam
-
Documentation Notes
-
Design issues with user events
-
Using NoSQL
-
Runtime Collections vs Metadata Collections
-
Anonymous authentication from browser app
-
Modules
-
Movement With Unity
-
Problem with url parameters for downloadables
-
Querying NoSql GameSparks database
-
Challenge accesType
See all 2341 topics