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
Additional context
I guess this has something to do with the computation of annotations "@odata.id" for which the required data is missing. The returned as per specs has the same type as the original entity set, but entities returned there are not original entities but aggregations instead, so any annotation should be null I guess.
While without odata.metadata=full the response is generated correctly, but "@odata.id" annotations are present (even if not requested), with the correct "null" value
The text was updated successfully, but these errors were encountered:
In my experience, if I explicitly select the property in the query on the basis of which the grouping takes place, no exception is thrown and the response is complete.
For example:
In my experience, if I explicitly select the property in the query on the basis of which the grouping takes place, no exception is thrown and the response is complete. For example:
Assemblies affected
ASP.NET Core OData 8.2.4
Describe the bug
When using the query option
$apply
withodata.metadata=full
the results an exception is thrown.Reproduce steps
Reproduce steps
A GET request to:
with header:
Throws:
Data Model
EDM (CSDL) Model
Additional context
I guess this has something to do with the computation of annotations "@odata.id" for which the required data is missing. The returned as per specs has the same type as the original entity set, but entities returned there are not original entities but aggregations instead, so any annotation should be null I guess.
While without
odata.metadata=full
the response is generated correctly, but "@odata.id" annotations are present (even if not requested), with the correct "null" valueThe text was updated successfully, but these errors were encountered: