Fix Fiori application to an old SAPUI5 version while upgrading the gateway to a newer one
Is it possible to fix a custom Fiori application (which is started from the Launchpad) to a specific SAPUI5 version? We have an custom application which is currently tested and working with SAPUI5 1.26.1. Is it possible to fix this application to always run on 1.26.1 and upgrade our gateway to SP14 (SAPUI5 1.28) or later versions? This is easy when the application is standalone (started from index.html), but the question is could this be done when the application is started from a Launchpad tile?
Thanks in advance!
Wouter Lemaire replied
Normally you can define the version in the SAPUI5 bootstrap by changing the SDK source. You can change the version in the url:
As you already mentioned, this is easy when to app runs standalone. But when it's started from the Fiori launchpad it will not go to the index.html, instead it will start from the component.js .
You can try to configure the SDK in the component.js metadata:
If that doesn't work, I would try to create a fiori tile based on the full url and not on a semantic object or launchpad configuration.
The last one will be the easiest way