Hi Stuart,
I can confirm we updated 3 servers to 2.1.20 (PAL, PASS, PAW). I updated our ticket this week to ask if it could have anything to do with the fact that we are setup to use OKTA for authentication and our user folders are stored under ...\Data\Okta\<user> instead of te default ..\Data\<user>. The response I got was that the defect has not been resolved yet.
Here is the test we ran:
- Admin opens the ..\data\okta\User folder on the PAL server to monitor
- subfolders exist containing subsets
- User logs in and starts running reports / viewing data
- Admin logs into PAW and opens the dimension editor
- makes a change using Reserve/Commit/Release
- On the PAL server, the subfolders that contain private subsets for the active User are completely deleted (does not impact users who are not logged in)
We have seen it delete subset folders that are NOT related to the dimension that was being updated. For example, we update Company .... and Company, Department and Network subsets are deleted. But this does not always occur. Sometimes it's just one folder that gets removed. In the attached snapshot, notice only the Company folder was impacted (before and after screenshots).
It's difficult to restore from backup because we have to first isolate the individual users who were impacted and then validate time stamps to make sure we don't overwrite newer subsets.
For now we are trying to avoid using the functionality, but we have multiple admins so it's not a great solution.
------------------------------
Arden Miller
Gray Media
------------------------------
Original Message:
Sent: Fri June 05, 2026 07:14 AM
From: STUART KING
Subject: PAW Dim Editor - Reserve/Commit/Release feature DELETES active user's private subsets
Hi Arden,
This sounds very familiar to an issue we addressed in a recent release of TM1. Can you confirm if you also updated TM1 Server, or just PAW? The issue was addressed in TM1 (not PAW) 2.1.20 was specific to Aliases on subsets being removed when using the reserve/commit functionality.
The implementation of the dimension editor Reserve function is simply making a copy of the dimension with the SaveAs REST API endpoint. While the dimension is 'reserved' the user is actually making changes in the copy of the dimension. When the user commits the changes, we do another SaveAs and overwrite the original dimension. This is a bit different than the Reserve/Commit functionality in the legacy client tools (the legacy client tools don't support a release the dimension to discard changes).
------------------------------
Stuart King
Product Manager
IBM Planning Analytics
------------------------------