Fiori Elements UI not using OData V2 : CAP

[akhthaaralibadhusha]

Hi I have developed an CAP project where the it has a service and some entities. I have used 

@Sisn/cds-odata-v2-adapter-proxy to change to CAP Odata to V2. Now the service is served by 2 URLs, "service/<Entity>" , "v2/service/<Entity>. When I develop a Fiori elements based application on top of this CAP app, it defaults to OData V4.

manifest.json

"dataSources": {

     "mainService": {

          "uri": "/service/",

          "type": "OData",

          "settings": { "annotations": [], "odataVersion": "4.0" }

     }

}

I tried to replace the URI to "/v2/service" , but UI is not getting initialized, rather it throws error on OData Meta Model ( I think it is specific to OData V4 ).

Please let me know what is the fix.

[Swetha__Balusamy]

I am also facing the same issue. Please let me know if you have found the solution

[junwu]

I think you have to recreate your ui project based on v2 model.

you cannot convert v4 FE project to V2 FE by just changing a odatamodel.

[akhthaaralibadhusha]

Is it possiible to recreate Fiori Elements project using OData V2, or I can do only Freestyle development

[junwu]

yes, you can recreate.

[akhthaaralibadhusha]

I created a fiori elements app, and selected Local CAP Project as backend, still it is falling back to OData V4 version. Any clue how to fix it

[Former Member]

Hello @akhthaaralibadhusha 

If you are creating the new fiori elements application using the generator, it will fallback to OData v4. You can try to change the new application properties to make it work, but I would personally deploy this CAP backend first and then create a new fiori elements based on the OData V2 endpoint (using the "Connect to a system" or "Connect to an OData Service" option in the generator).

Best regards,
Rafael