Skip to Content

Concurrency Control using ETags in a SAPUI5 application

Dear UI5 Developers,

in a SAPUI5 application concurrent editing of resources leads to a lost update problem. This means when two users edit the same resource at the same time one of the users will lose his changes. This paper describes how to use ETags within a SAPUI5 application in order to manage this scenario:

Kind regards,


You must be Logged on to comment or reply to a post.
  • Hi Matthias,

    Thanks for sharing.

    I might be wrong but I believe if we use the OData version 2 (sap.ui.model.odata.v2), the pages 4 and 6 will be wrong or unnecessary when you wrote:

    • Page 4 (method read):
      • async: true,
    • Page 6 (method update):
      • merge: true

    As I understand the data.v2 is always async=true and the default update method is Merge. Also the V2 API does not have both parameters.

    See: SAPUI5 SDK - Demo Kit