The UI5 release notes for version 1.143 đź”— contain the following announcement:
“The option to use the SAPUI5 OData V4 model with an OData V2 service is now deprecated.”
In the API documentation for OData Model v4 đź”—, this reads as:
“The version of the OData service. Supported values are “2.0”, “4.0”, and “4.01”. Note: “2.0” is deprecated since 1.143.0. We recommend migrating your service to OData V4.”
Important This does not mean that OData v2 is deprecated. It does not mean that you need to migrate your OData v2 services to v4.
The API documentation might confuse if you are not reading also the release notes. Especially the deprecation part can be interpreted as: v2 is deprecated, migrate your v2 OData service to v4. However, this is not the case. There is no need to migrate your OData v2 services to v4. OData v2 is supported in UI5. You can use your OData v2 services without any support problems or having to deal with any deprecation notices. The deprecation of OData v2 is for the case when the ODataModel v4 from UI5 is used to consume a OData v2 service đź”—.
For the rare (?) case when you wanted to treat a OData v2 service in your UI5 app as a v4 service, the sap.ui.model.odata.v4.ODataModel class allowed this. The class made some adjustment to make the v2 model look like v4. This feature was used when you were in the process of migration to v4, but your service was not ready but you wanted to develop the UI5 app already with v4 in mind. However, this was never a full replacement for all v4 features and worked only for read access.