Destinations

[YanGerzon]

Hi,

I want to make a fiori app that consumes odata from a sap byd report and shows it in a report list screen.

What kind of destination do i need to create? with what properties?
here is an example of a url to a report in BYD:
https://my******.sapbydesign.com/sap/byd/odata/ana_businessanalytics_analytics.svc/RPSRMPO_B02_Q0004...

As you can see the URL is a query to a specific entity set inside ana_businessanalytics_analytics.svc.
I would prefer to make a distination directly to the entity set instead of to ana_businessanalytics_analytics.svc but no matter how i try it will not pass authentication/connection test.

[Dinu]

If you are looking at the check connection button in the destination screen in cockpit, don’t. What it does is relevant only in cases where authentication is not required.

But for odata, consumers normally want to look at metadata. So most consumers would like to have the destination pointing to the service and not to an entity collection.

[yaniv200976]

Hi, thanks for the reply.
"What it does is relevant only in cases where authentication is not required."
What do you mean? you mean that when i check the connection it doesnt actually do it right?
cause when i provide it with the service url and use basic authentication it doesnt indeed succeed.

Ultiamtely i just want to understand how to work with this.
https://my******.sapbydesign.com/sap/byd/odata/ana_businessanalytics_analytics.svc/RPSRMPO_B02_Q0004QueryResults

when I create a connection using this :
https://my******.sapbydesign.com/sap/byd/odata/cust/v1/test/PurchaseOrderCollection
so first https://my360127.sapbydesign.com/sap/byd/odata/cust/v1/test/ and then i pick PurchaseOrderCollection, my fiori app works properly anf my report list shows the appropriate colums i have exposed in my odata service.
but I cant get the first service to work.

[Dinu]

The button only tries to access the URL. Even if there is any authorization configured, it does not use the configuration. So don't be worried by its results.

If you are building a Fiori application, it is best to configure a destination for the root of your services. That way you can use the same destination for accessing several services. By root, I mean what is the common prefix for the different services. The rest can go into the data source configuration of the Fiori App. But if your case is that the service name is not known beforehand or varies, you will need to include the service name also in the destination.

The entity collection name should not be in the destination. The data source for UI5 application is configured for the oData service. The entity collection name comes one level after the service.

For your case, I would suggest only to put "https://my******.sapbydesign.com" in the destination. I assume that the rest does not change from system to system. This way some one who configures the destination has less opportunity to make an error.

[YanGerzon]

But when i setup a fiori application it requires an odata service.

[Dinu]

First create a destination as outlined in BAS documentation.

Then follow these instructions to Connect to an OData Service with a Customized URL from documentation of Fiori Tools.