HTML5 Application with Managed Approuter: sometimes prefix is added to URL

[MioYasutake]

Hi experts,

I have several HTML5 applications with managed approuter as shown below. Each of them is deployed by different MTA.

If I click on the Application Name, the app content opens in a new browser.

Looking at the URL, I noticed that some apps got GUID like prefix and some don't.

with prefix

without prefix

Does anybody know why some apps get prefix?

With prefixed app, I have the following issue. So I would like to know how I can get rid of this prefix.

https://blogs.sap.com/2020/10/16/using-ui5-libraries-in-cf-approuter/#comment-568293

Best Regards,

Mio

[mariusobert · Accepted solution]

My first guess would be that you see the prefix when you use instance-level destinations for the html5 app repo key and the uaa key. See here (full sample😞

modules:
  - name: hello-world-destination-content
    ...
    parameters:
          content:
            instance:

I would recommend that you don't remove the prefix as instance-level destinations provide a higher security and are therefore the recommended approach.

[MioYasutake · Accepted solution]

Thank you Marious, you're right.

I have changed the destination to subaccount level, and the prefix has gone.

With subaccount level destination, I was able to consume a library.

[vickyokrm · Accepted solution]

Marius, i faced difficulities with the instance level destionation due to the guid prefix while using the app as nested component. I have described the issue here in detail:
https://answers.sap.com/questions/13542958/nested-ui5-application-on-btp-launchpad-was-not-ac.html

[vbalko-claimate]

mariusobert how can we find out this guid in order to call endpoints through apps xs-app.json ?

with subaccount level destination - adding appId is enough.

But with instance level destination - is there a way to get that guid programmaticaly?

[Cmdd]

Hi Vladimir,

did you manage to solve this? I'm stuck here too

[vbalko-claimate]

No I wasnt able - and I`m still struggling with that problem (cannot use instance level destinations). Workaround is to use subaccount level destinations, but that is not ideal.

Does somebody found solution?