Specific $metadata URL

Loading the SuccessFactors /odata/v2/$metadata takes between 15 and 30 seconds to load (7.5MB). Yes, seconds… https://launchpad.support.sap.com/#/notes/2755175 specifies the options available to query the $metadata. Limiting the $metadata to the entities that are used in the UI5 app can greatly improve the performance of the app. Unfortunately, UI5 supports specifying specific URL query parameters, but as you can see in the KBA, SF only supports specific URL paths.

E.g. having a UI5 app that uses data from User, FormHeader and Photo entities, the $metadata URL would become: /odata/v2/User,Photo,FormHeader/$metadata

It is currently not possible with UI5 to configure this type of $metadata URL.

[piejanssens]

@stoehr That seems to be working fine! I never thought about trying actual OData calls on that base URL. Thanks!

[uhlmannm]

Hi Pieter,

security token handling with SFSF services is a bit complicated. To my knowledge, there are no plans to support the HEAD request. Hence for an OData V2 SFSF service, you will at least need to switch off the HEAD request using the model parameter disableHeadRequestForToken. Unfortunately, that is not all for now. The ODataModel would then send a GET request with the value Fetch for the token header which is, to my knowledge, also rejected by the SFSF server. There are internal discussions how to handle that but I cannot provide a date when an improvement would be available. For read-only applications, you may for now simply deactivate the token handling using the model parameter tokenHandling.

Best regards Mathias.