cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Adapt UI changes mistakenly done in Test client (210) instead of Dev (200) – how to properly revert

Gaug2101
Newcomer
0 Likes
192

We follow a standard landscape approach where client 200 is used for development/configuration and client 210 is used only for unit testing.

Originally, all development and configuration were done in 200, and the changes were moved to 210 for testing. After testing, a new requirement came to hide/edit some fields in a Fiori app.

While searching, I found the Key User role (SAP_UI_FLEX_KEY_USER) for Adapt UI, assigned it to a test user, and performed Adapt UI changes directly in client 210. I also activated those changes in 210.

Later, I realized this was incorrect, as Adapt UI changes should be created only in the development client (200) and then moved to 210 for testing.

To revert the mistake, I:

  • Opened Adapt UI in 210
  • Switched back to Original App and activated it

However:

  • There is no option to delete or discard Adapt UI versions
  • Older versions still exist (inactive)
  • I understand SAP does not support deleting UI Adaptation versions, only activating another version

My questions are:

  1. Is activating the Original App the correct and only supported way to revert mistaken Adapt UI changes done in 210?
  2. When I now create Adapt UI changes correctly in 200 and move them to 210 for testing, how can I ensure there is no conflict with the earlier versions created in 210?
  3. Are inactive Adapt UI versions (created earlier in 210) completely ignored once a new version from 200 is activated/published?
  4. What is the recommended best practice to avoid such conflicts when working across multiple clients (Dev → Test → Quality)?

Any guidance or SAP‑recommended approach would be appreciated.

Accepted Solutions (0)

Answers (0)