You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$compute takes a common expression and assigns it an alias that is, by default, included in the response.
We state the following:
"Computed properties SHOULD be included as dynamic properties in the result and MUST be included if $select is specified with the computed property name, or star (*)."
However, since a common expression could return an entity type, should $expand be used to explicitly include in a result?
The text was updated successfully, but these errors were encountered:
Note that we have Edm.Untyped, but a defined as Edm.Untyped must still return a structural type, and a must return an entity or collection of entities.
Proposal: $compute creates a dynamic property. That dynamic property may be structural or an entity (or collection of entities). If it creates a structural type then it is addressed as such ($select). If it creates an entity (or collection of entities) then it is addressed as an entity (i.e., $expand).
This is the same as any other dynamic property that could vary from instance to instance between an entity or structured property.
$compute takes a common expression and assigns it an alias that is, by default, included in the response.
We state the following:
"Computed properties SHOULD be included as dynamic properties in the result and MUST be included if $select is specified with the computed property name, or star (*)."
However, since a common expression could return an entity type, should $expand be used to explicitly include in a result?
The text was updated successfully, but these errors were encountered: