Everyone is using REST APIs nowadays, despite the fact that HTTP is an inherently unreliable protocol. So how to deal with "lost requests" and "lost responses"? Not a problem for GET requests: just repeat them if you get no answer - GET is "safe" and...
Seven years ago we published OData 4.0 as a set of OASIS Standards - now we have the next incremental, fully compatible "release": the OData 4.01 specifications – Core, JSON Data, JSON Metadata, and XML Metadata – are approved as OASIS Standards and ...
When I try to upload a new version of an XML file attached to one of my Community wiki pages, I get the following error message:
The following error(s) occurred:
Virus found in file :upload_d9501a77_068b_4d4d_9554_eaffcb9eb77e_000...
Four years after OData V4 became an OASIS standard, and two years after it became the ISO/IEC 20802 standard, the first “feature pack” for OData V4 has been officially published.
The complete set of changes is described in What’s New in OData Versio...
Usually REST APIs produce minimized JSON without any line breaks or indentation, which preserves bandwidth and is fine if a machine is reading the produced JSON.
If however the intended audience mainly consists of humans, e.g. if the JSON files need...
My idea was to use $filter instead of the action parameters, so the action call would become*/sap/opu/odata/sap/ZSC_IO_ODS_TO_FNR_SB/execute?changes_x_days_back='5'&$filter=Plant eq '1003' or Plant eq '1004'&sap-client=400Not sure how to achieve this...
my main goal is to highlight the possibilities and advantages to using different APIs with SAP solutionsGot it, and I like your blog My point is that despite GraphQL's appeal, adding it to your stack isn't for free. You need a "middleware" that pro...
consider a scenario where a Fiori application needs to retrieve information about customers and their orders from an SAP backendThere are several variations on this scenario:1. SAP already offers an OData API that contains both Customer and Order ent...
Actually OData has all of the cited benefits of GraphQL, for exampleavoid overfetching with $select, $filter, $top, and $skipavoid underfetching with $expand and retrieve related resources with one requestflexibility of data retrieval with the above ...
You're welcome! And please add your use case to OData TC issue https://github.com/oasis-tcs/odata-specs/issues/279 to give us real-world examples on which to test a potential specification extension.