Replies: 1 comment 1 reply
-
To add more context, below is a typical sequence reproducing the issue:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Following this sample I have created a dynamic OData service. The model starts empty and grows as requests are executed. The model is updated during
MatcherPolicy.ApplyAsync
, and the route values are updated accordingly.I have been able to use all the OData features (Select, Filter, OrderBy, Count, SkipToken, SetMaxTop) without any issues but certain requests with a filter 'break' the service, and following requests with a filter randomly error with a 500 status code although they worked previously.
The stack trace when that happens is the following:
Can a dynamic model prevent filtering from working properly?
Beta Was this translation helpful? Give feedback.
All reactions