Display of page map fails

[_axel_]

Hi,

When trying to open the page map for my application I get only the following result:

In addition I get the error message 'EntryNotFound (FileSystemError): ftfs:/c:/Users/I023412/CALM/ptm-lib-ui/src/app.json'.
The application information is 'all green':

I wonder whether the problem is not due to the fact that project contains only the frontend of the application, i.e. the cap based odata v4 backend is implemented in a separate project. On the other hand, the application can be previewed without problem which makes me thing that this is a technical issue with page map application.

Best regards,

Axel.

P.S.: As the problem seems to be related to the manifest.json, I attach this file to the post.

[_axel_]

I also noticed that the problem temporarily disappears (until I close and re-open the project in VS code) if I remove the last part of the manifest: 
"sap.ui.generic.app": {
  "settings": {
     "variantManagement": "Page",
     "smartVariantManagement": true,
     "showShare": false
   }
}

[Miguel-g]

Hello,

I had the same problem with a Fiori Elements App, but mine was based on an OData V4 Service, and found this explanation in the SAP Community:
https://community.sap.com/t5/technology-q-a/sap-fiori-application-model-page-map-not-loading/qaq-p/1...

However, their solution of updating the ux-specification package did not help in my case. For me, the page map didn't load right after the application generator created the app, even without any changes on my side. Therefore I determined that the CDS View was probably configured falsely and tried it with a different OData Service --> worked.

Greetings

Miguel

[_axel_]

Hi Miguel,

[_axel_]

Hi Miguel, Thanks a lot for your comment. My application is indeed based on a OData V4 service. But all fiori tool packages are up-to-date (cf. screen copy in my original post). Also, there are are SAP e-Learnings out there where the page map works perfectly fine for fiori element apps based on ODate V4 services. The point is that the page map is supposed to facilitate the development and the maintenance of the fe front-end. So I really believe that the probleme I describe is due to a but. Best regards, Axel.

[Miguel-g]

@_axel_ ahh okay, yes i also have different Apps where the Page Map works perfectly fine for a OData V4 Service. And then for another App suddenly the Page map didn't work. The only different thing was the OData Service, so i thought that that must be the problem. Greetings, Miguel 🙂