UIB page changes are not saved in multiple updateset scenarioDescriptionWhen multiple update sets exist, users cannot save page changes in UIB. This issue occurs when the application is connected to a source control system (like git), causing users to work on their own update sets. - By default, in platform/UI16 - users cannot update a record when there is a new version of the record in a different update set. Users will see a warning (as in below screenshot) when they open such records and have to either switch to the other update set (which has latest version) or their own update set to update the record. UIB doesn't handle update sets (in general) which would cause the page save to fail silently in this scenario. - UIB doesn't handle updatesets (in general) which would cause the page save to fail silently in this scenario.Steps to Reproduce Connect your app to version control (like git), which results in multiple update sets per user.User A who is in his UpdateSet-A, updates a page in UIB.User B who is in his UpdateSet-B, opens the same page and makes some changes and saves the changes.User B reloads the page in UIB. Expected: The page changes should be saved and retained even after refresh.Actual: The page changes are not saved.WorkaroundAfter carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to address this issue as a future product enhancement. In the meantime, you can use the following workaround until the issue is resolved. - Goto the platform/UI16 home page and switch to the current user update set using the update set picker (as in below screenshot). - Return to UIB, reload the page editor, make changes, and the page save should work now. Related Problem: PRB1830480