Symptom
Create a custom tile in the FLP module and would like to avoid the requests to /flex/personalization/v1/data and /keyuser/flex/keyuser/v1/data/
Environment
BTP
Reproducing the Issue
- Create a MTA app with multiple HTML5 apps
- Add a FLP module in this MTA
- Build and deploy this MTA app to the CF
- Access the Fiori Launchpad Runtime
- Open one of the app inside this custom Fiori Launchpad, it will send out two requests: /flex/personalization/v1/data and /keyuser/flex/keyuser/v1/data/
Cause
If the manifest states the application type is "application", the SAPUI5 core interpreting this as a full blown application with all consequences.
The SAPUI5 client sees an application and within the portal/launchpad services, every application needs these requests.
Resolution
1. Open the manifest.json of the app
2. Change the type to component, here is an example:
"sap.app": {
"id": "<id>",
"type": "component",
"i18n": "<i18nPathRelativeToManifest>",
"applicationVersion": {
"version": "<version>"
},
3. Rebuild and deploy the app to CF again
Keywords
how to, sapui5, FLP module, MTA, /flex/personalization/v1/data, /keyuser/flex/keyuser/v1/data/, avoid , KBA , CA-UI5-FL-CLS , Cloud Foundry UI Flexibility Service Functionality , Problem