Clarify service-defined bound functions used as $apply transformations

XMLWordPrintable

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

      Applied

    • Hide

      Rephrase the definition of such functions:

      Current:
      Service-defined bound functions that take an entity set as their binding parameter MAY be used as set transformations within $apply if the type of the ...

      New:
      Service-defined bound functions that take a collection of instances of a structured type as their binding parameter and return a collection of instances of a structured type MAY be used as set transformations within $apply if the type of the ...

      Show
      Rephrase the definition of such functions: Current: Service-defined bound functions that take an entity set as their binding parameter MAY be used as set transformations within $apply if the type of the ... New: Service-defined bound functions that take a collection of instances of a structured type as their binding parameter and return a collection of instances of a structured type MAY be used as set transformations within $apply if the type of the ...

      The current text in 3        System Query Option $apply makes an incomplete statement about the return type of such a function in a sequence of $apply transformations: “If it returns an entity set, further transformations can follow the bound function.” This leaves room to use also functions that return a value of a complex or primitive type, which does not fit to the general principle of “set in/set out” for all transformations and the result of $apply being a collection of instances.

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

              Created:
              Updated:
              Resolved: