-
Notifications
You must be signed in to change notification settings - Fork 349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
StartsWith/Endswith not supported when chaining Odata calls #1144
Comments
@henning-krause, your query |
@AlanWong-MS, I removed the old nuget package and updated everything else to the latest (prerelease) versions. Still got the same issue: SampleAppV2.zip And I don't think the Frontend project is the problem. The error occurs in the Middleware project. I do see the call
being passed to the Middleware and then the NotSupportedException is thrown in the Middleware process. And as I said, a simpler filter using only equals or greater than is translated correctly. |
@AlanWong-MS, any news on this one? |
@xuzhg, any thoughts on this issue? |
@AlanWong-MS, any news? |
I've just upgraded the sample application above to the latest pre-release version, but still, the error occurs. This should work, shouldn't it? |
This thread is pretty old but I ran into a similar exception and changing the EnableQuery decorator from: |
I have a scenario where I need to call a Service via another service:
Client -> ServiceA -> ServiceB
ServiceA and ServiceB both expose their data via OData. So when I call ServiceA with
it should query ServiceB, fetch the data and return it to the client.
I've attached a sample solution doing just that: SampleApplication.zip.
Note: The sample App needs to be run as Administrator, otherwise it's not allowed to control the ports. And Just my code needs to be disabled to get the actual error message.
For most queries, this works just fine and I can even filter on the DataItems, as long as I'm using operators like equals, greater than, etc.
But if I run this query:
I get this error:
I've used the latest stable nuget packages as of this morning.
Is this a bug or simply not possible?
The text was updated successfully, but these errors were encountered: