-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: V4.0_CS02
-
Fix Version/s: V4.0_CSD04
-
Component/s: Data Aggregation
-
Labels:None
-
Environment:
Applied
-
Proposal:
-
Resolution:
Section 6.3.2 Recursive Hierarchy specifies that "The value of the Qualifier attribute can be used to reference the hierarchy in Hierarchy Filter Functions."
Hierarchy filter functions make use of this concept, they accept a qualifier as first parameter.
All examples in the document apply this approach with top-level entities, i.e. part of the collection addressed by the resource path. E.g.:
GET ~/SalesOrganizations?$filter=$it/Aggregation.isdescendant(}}
{{ Hierarchy='SalesOrgHierarchy',Node='EMEA')}}
Using this approach also for hierarchies on entity collections related to the top-level entities would require identifying the node set on which the function operates, which is not possible (example: GET ~/Sales?
$filter=$it/SalesOrganization/Aggregation.isdescendant(
Hierarchy='SalesOrganization/SalesOrgHierarchy',Node='EMEA') leaves the set of sales orgs to consider as hierarchy unspecified )
Therefore it needs to be clarified if/that these functions with the references to hierarchies always operate on top-level entities given by the resource path.
This issue is also relevant for ODATA-1218, which introduces transformations for hierarchy processing that also expect such a qualifier as call argument.
- Related to
-
ODATA-1218 Enhance hierarchy processing
- Closed