Clarify behavior of aggregate on property paths with collection-valued properties

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • V4.0_CSD04
    • Affects Version/s: V4.0_CSD03
    • Component/s: Data Aggregation
    • None
    • Environment:

      Applied

    • Hide

      In section 3.1, extend the third paragraph (insertions surrounded by *):
      If paths are present, the corresponding navigation properties are implicitly expanded to make the properties part of the result representation. *For every collection-valued navigation or complex property in the path, the aggregate transformation considers the concatenated list of all instances identified by that property for the remainder of the path.*

      Show
      In section 3.1, extend the third paragraph (insertions surrounded by *): If paths are present, the corresponding navigation properties are implicitly expanded to make the properties part of the result representation. *For every collection-valued navigation or complex property in the path, the aggregate transformation considers the concatenated list of all instances identified by that property for the remainder of the path.*

      Example 53 illustrates a use case for such property paths:
      GET ~/Products?$apply=
      groupby((Name),
               }}{{aggregate(Sales/Amount with sum as Total))

      ODATA-1206 clarified that the aggregate transformation supports collection-valued navigation/complex properties in property paths.

      What is still missing for a complete definition is a description of the service behavior for the aggregate transformation applied on paths containing segments with collection-valued properties.

            Assignee:
            Unassigned
            Reporter:
            gerald.krause1
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: