fix: rest call from within fiori launchpad

[nicoschoenteich]

Hi @kevindass, I found a solution to the problem. If we properly define the rest endpoint as a data source and the corresponding json model in the manifest.json, we can consume the model in our view regardless of the environment (meaning local, BAS, standalone CF, Fiori Launchpad).

It's now working from within the Launchpad, too:

Turns out tinkering with the ajax call manually wasn't the best approach...

[kevindass]

Thank you @nicoschoenteich

[kevindass]

@nicoschoenteich
Could you help me to understand this solution provided:
In mta.yaml, the addition of “destinations” with name “reqres” would create new destination under “Service Instance: reqres-destination-service - Destinations”.
Question: Does adding “destinations” with name “reqres” of URL means we are hard coding API endpoint into mta.ymal or it would still use “destinations” created at sun-account level ”Connectivity->Destinations” with help of xs-app.json?

[nicoschoenteich]

Hi @kevindass,
Yes, you are right. We are hardcoding the endpoint for the destination in the mta.yaml in this case, but this doesn't mean we couldn't create another subaccount or instance level destination. We can create as many destinations with unique names as we like.
Best, Nico