[OASIS Issue Tracker] (ODATA-1136) Allow hierarchy filter functions for ancestors and descendants to return true for starting node

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Gerald Krause created ODATA-1136:
------------------------------------

             Summary: Allow hierarchy filter functions for ancestors and descendants to return true for starting node
                 Key: ODATA-1136
                 URL: https://issues.oasis-open.org/browse/ODATA-1136
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: New Feature
          Components: Extension for Data Aggregation
    Affects Versions: V4.0_CSD03
         Environment: Proposed
            Reporter: Gerald Krause
            Priority: Minor
             Fix For: V4.0_CSD04


The current definitions of the two hierarchy filter functions isancestor and isdescendant specify that the functions return true only if the current entity is a strict ancestor/descendant of the given start node.

Practical applications sometimes require the start node to be included in the result. For this purpose, both functions could be extended by an optional Boolean parameter that allows the OData client to specify, if the start node shall be included in the result. With this, the filter expression $it/Aggregation.isdescendant(Hierarchy='SalesOrgHierarchy',Node='EMEA',IncludeParent=”true”) could avoid the clumsier $it/Aggregation.isdescendant(Hierarchy='SalesOrgHierarchy',Node='EMEA') or ID eq 'EMEA'




--
This message was sent by Atlassian JIRA
(v6.2.2#6258)