From aceefd5d28bb577f852f0b88852dac4a0e212ba6 Mon Sep 17 00:00:00 2001 From: Joost Verhoog Date: Thu, 25 Sep 2025 08:46:30 +0200 Subject: [PATCH 1/3] 11.3.0 is clear about 'any' filter that it does not support --- .../published-odata-services/supported-odata-operations.md | 2 ++ .../published-odata-services/supported-odata-operations.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/content/en/docs/refguide/modeling/integration/odata-services/published-odata-services/supported-odata-operations.md b/content/en/docs/refguide/modeling/integration/odata-services/published-odata-services/supported-odata-operations.md index caf58fb5bbf..1582684ab7d 100644 --- a/content/en/docs/refguide/modeling/integration/odata-services/published-odata-services/supported-odata-operations.md +++ b/content/en/docs/refguide/modeling/integration/odata-services/published-odata-services/supported-odata-operations.md @@ -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 (e.g. `person`) more than once and refers back over the association (e.g. 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. diff --git a/content/en/docs/refguide10/modeling/integration/odata-services/published-odata-services/supported-odata-operations.md b/content/en/docs/refguide10/modeling/integration/odata-services/published-odata-services/supported-odata-operations.md index c5e7182c8f5..eb8176cf36b 100644 --- a/content/en/docs/refguide10/modeling/integration/odata-services/published-odata-services/supported-odata-operations.md +++ b/content/en/docs/refguide10/modeling/integration/odata-services/published-odata-services/supported-odata-operations.md @@ -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 (e.g. `person`) more than once and refers back over the association (e.g. 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. From 185077c7954f70159adb4081031b3e1aac7ff102 Mon Sep 17 00:00:00 2001 From: Quinn Tracy <142489060+quinntracy@users.noreply.github.com> Date: Thu, 25 Sep 2025 16:01:33 +0200 Subject: [PATCH 2/3] Small edit --- .../published-odata-services/supported-odata-operations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/refguide/modeling/integration/odata-services/published-odata-services/supported-odata-operations.md b/content/en/docs/refguide/modeling/integration/odata-services/published-odata-services/supported-odata-operations.md index 1582684ab7d..e036fbd8efb 100644 --- a/content/en/docs/refguide/modeling/integration/odata-services/published-odata-services/supported-odata-operations.md +++ b/content/en/docs/refguide/modeling/integration/odata-services/published-odata-services/supported-odata-operations.md @@ -122,7 +122,7 @@ 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 (e.g. `person`) more than once and refers back over the association (e.g. to the `Name` of the person) will result in `501 Not Implemented`. +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 From 6e35a041949b787a3278a613d8ae9f96df33c551 Mon Sep 17 00:00:00 2001 From: Quinn Tracy <142489060+quinntracy@users.noreply.github.com> Date: Thu, 25 Sep 2025 16:02:02 +0200 Subject: [PATCH 3/3] Update supported-odata-operations.md --- .../published-odata-services/supported-odata-operations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/refguide10/modeling/integration/odata-services/published-odata-services/supported-odata-operations.md b/content/en/docs/refguide10/modeling/integration/odata-services/published-odata-services/supported-odata-operations.md index eb8176cf36b..04d86641dd7 100644 --- a/content/en/docs/refguide10/modeling/integration/odata-services/published-odata-services/supported-odata-operations.md +++ b/content/en/docs/refguide10/modeling/integration/odata-services/published-odata-services/supported-odata-operations.md @@ -122,7 +122,7 @@ 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 (e.g. `person`) more than once and refers back over the association (e.g. to the `Name` of the person) will result in `501 Not Implemented`. +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