UI5 App dumps after Release update changes CDS View

[#1]

Hi,

after upgrading from S4CODE 105 to S4CODE 107 we have a problem with one of our custom UI5 apps.

This UI5 app uses CDS View 'C_ManageProductionOrder'.

CDS View 'C_ManageProductionOrder' changed significantly after the release update.

Here is just one part of the change:

Before release upgrade:

association [1..1] to I_MfgOrder as _MfgOrder on  $projection.ManufacturingOrder   = _MfgOrder.ManufacturingOrder

                                              and $projection.ProductionSupervisor = _MfgOrder.ProductionSupervisor

                                              and $projection.ProductionPlant      = _MfgOrder.ProductionPlant

After release upgrade:

association [1..1] to I_MfgOrderBasicFilter as _MfgOrder on  $projection.ManufacturingOrder    = _MfgOrder.ManufacturingOrder
                                                         and $projection.ProductionSupervisor  = _MfgOrder.ProductionSupervisor
                                                         and $projection.ProductionPlant       = _MfgOrder.ProductionPlant

association [1..1] to I_MfgOrderBasicFilter as _OrderVH  on  $projection.ManufacturingOrder   = _OrderVH.ManufacturingOrder

As you can see, 'I_MfgOrder' has been replaced by 'I_MfgOrderBasicFilter'.

So when '_MfgOrder' is being addressed, the underlying CDS View has a different structure.

What's the best practice here to fix the problems in our custom app?

Should I correct the structure manually in C_ManageProductionOrder.json?

Or is there any 'automatic' way to get the updated CS View structure into our WebIDE project?

[AlexNecula30 · Accepted solution]

It really depends on the way the custom app was developed. It could be as easy as regenerating the odata service in SEGW or more complicated like having to change the project in WebIDE and/or odata service. I suggest to give it to a developer.

[eyanosa · Accepted solution]

Thanks for your advice. Regeneration in SEGW did the trick. 😉