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
Having been advised to upgrade from v2 because of it's end of life I notice that basically grouping is broken, the current advice appears to be to generate a ticket for grouping scenario, I couldn't find one for this scenario so here it is ...
... this results in the well known issue that others reporting grouping problems are facing.
Solving this by the looks of things will fix at least 5 or 6 OData related tickets too.
Typical example from my web stack, I have an entity that looks like this ...
Having been advised to upgrade from v2 because of it's end of life I notice that basically grouping is broken, the current advice appears to be to generate a ticket for grouping scenario, I couldn't find one for this scenario so here it is ...
... this results in the well known issue that others reporting grouping problems are facing.
Solving this by the looks of things will fix at least 5 or 6 OData related tickets too.
Typical example from my web stack, I have an entity that looks like this ...
Running this query on EF Core 3.1 breaks, but works find on EF Core 2 ...
The text was updated successfully, but these errors were encountered: