Skip to content

11.3.0 is clear about 'any' filter that it does not support #10137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 1, 2025
Merged

11.3.0 is clear about 'any' filter that it does not support #10137

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
aceefd5
11.3.0 is clear about 'any' filter that it does not support
joostverhoog Sep 25, 2025
185077c
Small edit
quinntracy Sep 25, 2025
6e35a04
Update supported-odata-operations.md
quinntracy Sep 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions ...tegration/odata-services/published-odata-services/supported-odata-operations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -122,6 +122,8 @@ You can filter on the attributes of an associated entity. The syntax depends on

Filtering on an associated object or list in this way is possible only when you [expose associations as a link](/refguide/odata-representation/#associations). It is not possible when you expose associations as an associated object ID.

For many-to-many associations, some expressions that filter on an associated list are not supported. An example of such an unsupported filter is `City?$filter=HasLivedIn/any(person:person/Year le 1919 and person/Name eq Name)`, where the `HasLivedIn` association is many-to-many. For this request, the service will respond with `501 Not Implemented`. In general, an associated list filter on a many-to-many association that uses the variable (in this example, `person`) more than once and refers back over the association (in this example, to the `Name` of the person) will result in `501 Not Implemented`.

##### Arithmetic Operators

The use of arithmetic operators such as `add`, `sub`, `mul`, `div`, and `mod` in filter expressions is not supported.
Expand Down
2 changes: 2 additions & 0 deletions ...tegration/odata-services/published-odata-services/supported-odata-operations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -122,6 +122,8 @@ You can filter on the attributes of an associated entity. The syntax depends on

Filtering on an associated object or list in this way is possible only when you [expose associations as a link](/refguide10/odata-representation/#associations). It is not possible when you expose associations as an associated object ID.

For many-to-many associations, some expressions that filter on an associated list are not supported. An example of such an unsupported filter is `City?$filter=HasLivedIn/any(person:person/Year le 1919 and person/Name eq Name)`, where the `HasLivedIn` association is many-to-many. For this request, the service will respond with `501 Not Implemented`. In general, an associated list filter on a many-to-many association that uses the variable (in this example, `person`) more than once and refers back over the association (in this example, to the `Name` of the person) will result in `501 Not Implemented`.

##### Arithmetic Operators

The use of arithmetic operators such as `add`, `sub`, `mul`, `div`, and `mod` in filter expressions is not supported.
Expand Down