Скачать или смотреть Handling Reserved Keywords like value in Azure Cosmos DB Queries

Learn how to avoid query errors caused by reserved keywords such as `value` in Azure Cosmos DB by using proper query syntax and property access methods.
---
This video is based on the question https://stackoverflow.com/q/79531906/ asked by the user 'user3732793' ( https://stackoverflow.com/u/3732793/ ) and on the answer https://stackoverflow.com/a/79531967/ provided by the user 'Matias Quaranta' ( https://stackoverflow.com/u/5641598/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: select value does fail in cosmo db

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to drop me a comment under this video.
---
Avoiding Reserved Keyword Issues in Azure Cosmos DB

When querying Azure Cosmos DB using SQL API, certain keywords are reserved and can cause query failures if used as property names without special handling. One common example is the property name value.

The Problem

Consider a Cosmos DB container with items like:

[[See Video to Reveal this Text or Code Snippet]]

A query like this successfully works:

[[See Video to Reveal this Text or Code Snippet]]

But this query:

[[See Video to Reveal this Text or Code Snippet]]

throws an error:

[[See Video to Reveal this Text or Code Snippet]]

This is because value is a reserved keyword in Cosmos DB SQL syntax (used in statements like SELECT VALUE ...).

The Solution

To safely query properties named with reserved keywords, you have two main options:

1. Use Bracket Notation

Instead of d.value, use bracket notation to access the property:

[[See Video to Reveal this Text or Code Snippet]]

This explicitly treats value as a property name, bypassing the keyword conflict.

2. Rename the Property

If possible, avoid naming properties with reserved keywords. For example, use val or myValue.

Notes

Always check the official list of reserved keywords when designing your document properties or writing queries.

Using bracket notation is an effective way to query without renaming properties.

Summary

value is a reserved SQL keyword in Cosmos DB

Queries using d.value will fail

Use d["value"] syntax to access such properties safely

Prefer unique, non-reserved property names when designing your JSON schema

Following these practices leads to cleaner queries and avoids runtime failures caused by reserved keywords.