With the latest release of the SAP Cloud SDK, we have introduced a beta version of the Java client library for the SCP Workflow REST API.
Goal of this Blog Post
We are happy to announce that SAP Cloud SDK for Java 3.19.1 introduces beta support for t...
In June 2020 we have launched a brand new documentation portal which consolidates all the knowledge, feature documentation, comprehensive guides, video tutorials, troubleshooting, release notes, API documentation and more. Please, use it as a single ...
I have created a custom CDS view in my local package as follows:
@AbapCatalog.sqlViewName: 'ZMD_C_PUR_REQ3'
@AccessControl.authorizationCheck: #NOT_REQUIRED
@EndUserText.label: 'Consumption View Purchase Requisition'
@ObjectModel.semanticKey: 'ban...
I generated an OData service out of an CDS consumption view using @Odata.publish: true.
I am using the transactional processing provided by these annotations:
@ObjectModel.transactionalProcessingDelegated: true
@ObjectModel.createEnabled: true
...
In June 2020 we have launched a brand new documentation portal which consolidates all the knowledge, feature documentation, comprehensive guides, video tutorials, troubleshooting, release notes, API documentation and more. Please, use it as a single ...
edwin_sendjaja34 The OData metadata of that API is now updated and consistent, the OData client generation works now.You can download the working metadata here: https://api.sap.com/api/ECTimeOff/overview?name=ECTimeOff&type=EDMX∾tion=download&artifac...
Hi Edwin,I can reproduce the same issue also with version 3.0.0 of the OData VDM Generator.As mentioned, we'll check internally with the responsible colleagues to make the OData API metadata consistent.ThanksMarco
Hi Edwin,thanks for reaching out to the SAP Cloud SDK team.I can confirm that the OData metadata of the Time Off API causes problems. It seems that the metadata is not fully consistent. We'll check internally with the responsible colleagues.For the ...
The provided stacktrace reveals that the Cloud SDK fails to determine the logged-in principal in your app. Does your app have a protected backend and can we assume that the thread is triggered by an incoming request that contains a JWT in the request...
