Business Application Studio-Fiori Tools - Fiori app generation broken for RAP-based OData V4 service

[saurabh__khare]

Hi,

Environment details:

Backend - SAP S4HANA 2022 FPS02

SAP Business Application Studio Version: 1.93.1

UI5 Version 1.108.30

I am encountering a strange issue in SAP Business Application Studio (BAS) while generating a Fiori List Report for a RAP-based OData V4 service. Despite the service being explicitly defined and recognized as OData V4, BAS/Fiori Tools incorrectly treat it as an OData V2 service and generate faulty configurations.

This issue affects all my previously deployed V4 services, which worked successfully earlier. However, when redeploying these services as duplicate apps for testing, BAS incorrectly interprets them as V2 services. As a result, the generated application is broken and fails to function both during preview in BAS and after deployment.

The app fails to load with the following errors:
"[ODataMetadata] initial loading of metadata failed"

"Invalid metadata document."

It is important to note that the same application and service work perfectly fine when previewed locally through Eclipse, which confirms that both the app and the generated OData V4 service, metadata are correct. 

Is anyone else facing a similar problem? App generation and deployment has worked absolutely fine in the past with the exact same steps.

Best Regards,

Saurabh

[cesar_gr]

Hi we have the same problem

[cesar_gr]

We have the same issues from this weekend. We found that the last time that we create a project with odata V4 the wizard doing this ok, but yesterday we create an deploy an application and the code are generated with issues as you mention

[saurabh__khare]

Thanks, Ian for the quick turn around. That seems to have fixed the problem. I'm able to generate a template-based Fiori app for OData v4 service now.

Just a side-note - For those who had downgraded the Fiori generator as per the suggested temporary workaround using 

npm i -g @sap/generator-fiori@1.15.7

would have to install the latest version manually even after restarting the dev space using

npm i -g @sap/generator-fiori

npm package list after restarting the dev space:

user: ########### $ npm -g list
/home/user/.node_modules_global/lib
└── @sap/generator-fiori@1.15.7

After installing the latest Fiori generator:

user: ############ $ npm i -g @sap/generator-fiori

changed 39 packages in 2s

9 packages are looking for funding
  run `npm fund` for details
Reshimming asdf nodejs...
user: ############ $ npm -g list
/home/user/.node_modules_global/lib
├── @sap/generator-fiori@1.16.1

In short, restarting the dev space does not auto-update to the latest Fiori generator if you had manually downgraded previously. You would have to upgrade manually.
Having said that, the latest Fiori generator(1.16.1) works fine for OData v4 services. @IanQuigley : Can you please confirm if the presence of /IWBEP/COMMON services is expected in the service selection list?

Regards,

Saurabh

[IanQuigley]

Hi Saurabh, it might take a little while for your dev space to update with the latest, but it should happen when the new version is released. Hopefully soon for customers, but thanks for mentioning the workaround. In terms of V4 services displayed, nothing should have changed here with the latest fix - the V4 list of services should be the same. Thanks.

[saurabh__khare]

Hi Ian. Thanks. With 1.15.7 I did not see the /IWBEP/COMMON (0001) services in the list. They have started appearing 1.16.0 onwards.

[IanQuigley]

Hi Saurabh. In 1.16.0 we did fix a bug regarding the list of services available in the catalog. In some cases the full list of services was not being returned. This was fixed in 1.16.0, so no difference between 1.16.0 and 1.16.1 in that regard. However, you are correct in that there is a difference between 1.16.1 and 1.15.7, as the fix only came in after 1.15.7. I hope that helps. Regards, Ian