3153626 - Private version shared with multiple users does not allow data entry

• A private version is shared with write access to multiple users.
• At some point, the version is no longer editable by any user.
• In the audit log and chrome trace the error "version [XX] currently in use by user [USERID]"
• The error occurs even if the user mentioned is no longer logged in.

SAP Analytics Cloud 2022 QRC1 release and earlier

1. Create a private version filtered to a specific set of dimensions and share it with write access to one or more users
2. Create another private version filtered to a different set of dimensions and share it to the same users with the same name
3. Create one or more stories with tables that have mass data entry enabled
4. Once the stories are published and used by multiple users, this issue may eventually occur

There is a known issue that can cause a private version to remain in a locked state if there are multiple versions with the same name in edit mode at the same time.

The exact combination of steps to cause the lock is not known, but this issue has been reported in cases where users have multiple copies of private versions shared with them with the same name.

The development team is working on a fix for this issue.

Until a fix is identified, when sharing private versions, please ensure a end user will not get multiple private versions with same name.

A workaround to release data locks if this issue occurs may be by trying to do single data entry on a newly opened/refreshed SAC page.

This should generate a popup dialog popup indicating to the user that the version is in use(locked).

A "Stop" button in the dialog will release the unexpected locks.

KBA , LOD-ANA-PL-DE , Data Entry and Mass Data Entry , LOD-ANA-PL-DA , Data Actions , Problem