I am trying to query the v4 endpoint of the odata content service with no luck. The reason I want to use that endpoint is because odata's v4 has more "filtering" options and more advanced querying functions. However unless I query for metadata or to see the entities:
I get different exceptions, for example using POSTMAN:
I've also tried using the "automatically generated proxies" (which work when generated against the v2 endpoint) and I get this error too:
DataServiceClientException: {"error":{"code":"1800","message":"This query is not supported: http://service-url-goes-here:8081/client/v4/content.svc/ComponentPresentations?$top=1"}}
I've spent a good full day trying serveral things, and I am starting to think that either the v4 endpoint is not ready for use or that I might have the content service not properly configured to use such endpoint.
Any pointers would be highly appreciated.
UPDATE I decided to switch to CIL, instead of doing my thing. However when using the API I get the following exception: Invalid v4 service endpoint for content-service
Which tells me that I was kinda right with the assumption that my v4 endpoint (or the content service all along) might not be properly configured. I went over the documentation over and over and checked my discovery service, which has the content service properly configured pointing to the right server. I added the configuration settings in my web.config with the oauth properties and the discovery service uri:
