Object Page error after generation

[former_member624584]

Hi guys,

I've created a small cap service and created with the fiori tools a list report page. The list page is working fine. However, when I navigate to the object page (displayed in the master detail layout) I receive an error 'A technical error has occurred, Cannot read property 'Value' of undefined'

Is there a way of debugging the fiori elements app, so I could solve the problem?

Here is the project: https://github.com/ThorstenSAP/nutritionTracker/tree/feature/FioriUI

Thank you,

Thorsten

[former_member283911 · Accepted solution]

Hi Thorsten,

I've created a fork with some changes to make the project compatible with Fiori tools. See

https://github.com/ThorstenSAP/nutritionTracker/compare/feature/FioriUI...devinea:feature/FioriUI

Object page loads now.

Also, I moved uimodule to app/uimodule as app is the default folder for webapps in CAP.

You appear to have created your project using the Fiori Generator using the odata url.

Fiori generator supports using the CAP project as a datasource (instead of the odata URL)

https://help.sap.com/viewer/17d50220bcd848aa854c9c182d65b699/Latest/en-US/99061814ead548808d539861fb...

This has the advantage of using CAP CDS based annotations instead of XML/EMDX annontations and better integration with Fiori tools.

I added an example project at https://github.com/devinea/nutritionTracker/tree/feature/FioriUI/app/uimodule_cap

[former_member624584 · Accepted solution]

Hi Austin,

Thanks for helping me. I just checked your fork and it seems like that some annotations were missing (I got it running now).
Are there known advantages of using cap cds based annotations? In the project I several branches, one using the cap cds based annotations whereas an other branch uses the fiori elements annotations, to get to know the differences between the development styles.

Cheers,
Thorsten

[former_member283911]

Hi Thorsten,

Either form of annotation can achieve the same end result.

Fiori tools supports both CDS and EDMX based annotations.

For CAP it seems more natural to use the same CDS syntax for the whole project.

Fiori tools CDS support means that it is working with the latest service definition always.

If you are using EDMX the metadata.xml needs to be sync'd from the server after the service has been updated.

This is supported by Service Manager (right click menu on manifest.json).

Regards,

Austin