Issue Configuring oData Service in SAP WEbIDE full stack (cloud)

[former_member243729]

Hi,

I am able to configure datasource in the manifest.json file using 'descriptor editor' tab but when I do this I see the uri is being prefixed with the destination name (like below).

"uri": "/<desinationName>/sap/opu/odata/sap/<ServiceName>/"

Though the applications runs fine on webide, it fails when I deploy on to the gateway system ...the application launch fails since the service uri path is not recognized and it throws 'failed to load oData metadata'.

May i know how to avoid having the destination name prefixed to the data source URI.

In the past when I never had this issue but with my new login to webide (may be something in the destination creation I did not do right) I see this issue.

Any help/suggestions would be appreciated.

[former_member243729]

So one thing I just noticed is that in the neo-app.json I see below entry.

{ "path": "<destinationName>", "target": { "type": "destination", "name": "<destinationName>"}, "description": "<destinationDescription>" }

when I made changes to this entry as below, and also removed the destination name from the URI in the manifest.json, it worked fine..I mean I was not getting oData Metadat land failed issue.

{ "path": "/sap/opu/odata", "target": { "type": "destination", "name": "<destinationName>", "entryPath": "/sap/opu/odata" }, "description": "<destinationDescription>" }

But can anyone help me know why in first place the entries are getting incorrectly and I had to change them manually (though one time activity) ?