cancel
Showing results for 
Search instead for 
Did you mean: 

Failed to perform CRUD operations from appgyver using SAP sample backend OData service.

0 Kudos

Hi experts,

Recently I configured appgyver by consuming SAP sample backend service which is available in SAP BTP as odata integration. When we try to perform any crud operation from appgyver we are getting an error as shown below:

SAP BACKEND ODATA URL : https://mobile-service-cockpit-web.cfapps.eu10.hana.ondemand.com/cockpit/v1/org/810726b9trial/space/...

When we try to update while configuring the odata service we are getting an error as below:
Even if the status is mentioned as ok , but when check the response the value is getting updated to the desired one. It is displaying the original record.

EsmeeX
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Priya,

Could you please share your app ID? It's the 6 digit number in the URL when you have your app open. We can look to make sure that everything is working as expected with the CORS proxy.

0 Kudos

Hi,
App ID :331260

EsmeeX
Product and Topic Expert
Product and Topic Expert

Hi Priya, we're still looking into this. It seems to our CORS loundry service supports anything but “GET”. So if the OData service does not have CORS headers, update, create and delete on the test tab would not work. We are looking into a fix on the CORS loundry side.

0 Kudos

Thanks for the information Esmee Xavier!

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

Hi Esmee Xavier,

Thanks for the reply,

I tried the crud operations using a different odata service(S7H) which allows crud operations when used in a different application(Asset manager).Initially, while performing the update operating during the configuration of the odata service in the AppGyver platform I was getting "status as ok"(Even though it did not fetch the updated record but the original record) along with the cors error. But today, when I tried the status is showing 403 along with the cors error. We tried this with different users in the appgyver platform it is throwing the same status as 403 along with the cors error.

I tried performing the crud operation from the application as well , still getting the same CORS error.

I would also like to add that we are using the free version of appgyver and the trial version of SAP BTP. So, appgyver is not present under the list of entitlements in the trial account of BTP.

EsmeeX
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Priya, a fix has been issued to enable update operations in CORS restricted services. On a separate note, we tested this particular service with your credentials and the update request fails with the “Forbidden” message, so the API may not have update capability for your username at least. List and retrieve operations should work as expected.