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
The resulting query now contains the proper underlying int value of 0 for StatusOne, while it contains the name of the enum field "Active" for property two:
some_entity?$filter=StatusOne eq 0 and StatusTwo eq 'Active'
I would expect both cases would use the underlying int value. Would love to see a fix for this.
The text was updated successfully, but these errors were encountered:
Let's say you have an enum called Status and an entity with 2 properties. One property is of type Status, and the other is of type nullable Status.
Imagine we now create a query with a filter on these properties like so:
The resulting query now contains the proper underlying int value of 0 for StatusOne, while it contains the name of the enum field "Active" for property two:
I would expect both cases would use the underlying int value. Would love to see a fix for this.
The text was updated successfully, but these errors were encountered: