odata-query | OData v4 query builder | Autocomplete library
kandi X-RAY | odata-query Summary
kandi X-RAY | odata-query Summary
OData v4 query builder
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of odata-query
odata-query Key Features
odata-query Examples and Code Snippets
Community Discussions
Trending Discussions on odata-query
QUESTION
I am implementing the OData in my .netcore project and I am trying to apply some filters. When I use odata/productshops?$filter=SellingPrice eq 20
, I get the product with the selling price 20.
But when I try to filter all product with selling price greater or equal 20:
odata/productshops?$filter=SellingPrice ge 20
I got an internal server error saying:
...ANSWER
Answered 2021-Feb-27 at 16:17This is most likely caused by sending wrong query to database. My guess is you are calculating SellingPrice outside of Query Method and that is causing the issue.
(I would post this as comment but I still dont have enough reputation - Sorry!)
QUESTION
Should it be possible to provide an $expand=singleValueExtendedProperties...
query parameter on an events delta request? My approach returns an error that I wasn't quite expecting.
The request looks like this:
...ANSWER
Answered 2020-Aug-06 at 15:40The error you are receiving is actually a bug in the library the service is using, see this issue and that issue.
You should be receiving an error saying that the request is not supported.
Even when the parsing bug gets fixed, it's unlikely to work as schema and open extensions are stored in another system than the resource and providing a unique delta token containing a watermark valid for both systems is not implemented today. You can request support for it on uservoice.
QUESTION
I am trying to query my OData service for a data with a datetime greater or equal to given value. It is not working as expected
I have read the documentation:
https://docs.microsoft.com/en-us/odata/webapi/datetime-support#filter-datetime
Assemblies:
- Microsoft.AspNetCore.OData 7.4.0
- NET Core 3
- EF Core
Reproduce steps
I have tried the following query formats:
https://myurl/api/resource?$filter=city eq 'Kigali' and purchaseDateTime gt 2020-01-01T23:59:59.99Z &$orderby=purchaseDateTime desc
HTTP 500 - Conversion failed when converting date and/or time from character string.https://myurl/api/resource?$filter=city eq 'Kigali' and purchaseDateTime gt cast(2020-01-01T23:59:59.99Z,Edm.DateTimeOffset) &$orderby=purchaseDateTime desc
returns HTTP 500 - Internal Server Errorhttps://myurl/api/resource?$filter=city eq 'Kigali' and purchaseDateTime gt datetime'2020-01-01T23:59:59.99Z' &$orderby=purchaseDateTime desc
On the OData site, this works
Expected result
Return the data according to the query in the same way that the the http://services.odata.org responds
Actual results
HTTP Bad Request or HTTP 500
Microsoft says this should work:
...ANSWER
Answered 2020-Aug-03 at 02:33For your first two queries, it works for me.
QUESTION
I'm building a Spring Boot project making use of S/4HANA custom OData Service and Java VDM. I have been following various tutorials on SAP Blog, developer.sap.com or S4H13 course - the approach is pretty much the same. I managed to successfully generate VDM for my Custom OData Service based on the edmx file, created all necessary commands, methods in the controller and so on.
Unfortunately, I'm encountering an issue when launching the project locally.
I use the following command first: mvn clean package
and later, when I'm in the application directory want to run the project: mvn spring-boot:run
.
The project build fails with the following errors and exceptions:
2020-07-31 12:45:20.941 ERROR 70176 --- [main] o.a.c.c.C.[Tomcat].[localhost].[/] : Exception sending context initialized event to listener instance of class [com.sap.cloud.sdk.s4hana.connectivity.ErpDestination]
ANSWER
Answered 2020-Jul-31 at 13:16Please find the outdated dependency in your dependency tree:
QUESTION
I am not able to move forward due to an exception thrown by Cloud SDK. EdmNamedImpl class of cloud SDK is throwing an error due to incorrect SF Metadata property name. The property name of the SF entity is "goto-url", so due to hyphen in field name is not being accepted by PATTER_VALID_NAME matcher. I have tried many approaches but could not get around this exception. I guess Cloud SDK either should provide a way to suppress name validation or a way to pass path of local metadata file to execute method of FluentHelper.
The way I am constructing Query is:
...ANSWER
Answered 2020-Jun-16 at 09:38Unfortunately I currently see no easy way around this. The SDK itself internally uses another library to perform OData 2.0 requests. The library performs the metadata request and processes it before issuing the actual request.
However, as shared in this answer a hyphen is not legal within entity identifiers. So this is more of a problem on the SuccessFactors side of things.
Edit:
There is a beta API in place that does not rely on metadata requests but requires you to assemble the request manually:
QUESTION
I need to modify the $filter
on the server-side of .NET core 2.1 API. I have looked at these:
https://entityframework.net/knowledge-base/33660648/odata-v4-modify--filter-on-server-side
OData V4 modify $filter on server side
The best way to modify a WebAPI OData QueryOptions.Filter
(and a couple of others)
They all do something along the lines of:
...ANSWER
Answered 2020-Apr-15 at 11:29@Xaphann You could extend EnableQueryAttribute
in the manner below:
QUESTION
Using this SharePoint OData query:
...ANSWER
Answered 2020-Apr-06 at 02:57No endswith based on official documentation.
When your list data over 5000 items, you can't filter item based on a none-indexed column as throttle limit in SharePoint, you need add the column as indexed so you could filter based on it.
QUESTION
I am getting the issue described up above when running integration tests.
The full error message follows:
...ANSWER
Answered 2020-Mar-25 at 13:55Looking at the dependency tree, I can see that there is a mix-up of SDK dependencies of version 2 and 3 in your project which is causing the issue.
The dependency entries with groupId starting with com.sap.cloud.s4hana
are mostly v2 dependencies and the ones with groupId starting with com.sap.cloud.sdk
are v3 dependencies.So, please use this as a reference to convert all v2 dependencies to the corresponding v3 dependencies.
Alternatively, you can also include the sdk-bom
dependency (groupId: com.sap.cloud.sdk
, artifactId: sdk-bom
) in your pom with a version
, so that you can start including other sdk dependencies without explicitly including the version
information.
This would also ensure that all the sdk dependencies you include would always fall into the a particular version:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install odata-query
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page