Problem Note 67679: An original scenario becomes locked when you create a copy of it by using the "Save as" option in SAS® Customer Intelligence Studio
In SAS® Customer Intelligence, creating a copy of a scenario by using the Save as option causes the original scenario to be locked. This problem happens when you open a scenario (for example, Scenario1) and you use the Save as option to create a copy of that scenario with another name (for example, Scenario2). When you do this, Scenario2 opens. However, Scenario1 is locked.
When you try to open Scenario1, the following message is displayed:
If you select Locks on the Administration tab, you can see that Scenario1 is locked. This behavior is different from earlier releases of the software, where the original scenario is unlocked after you create a copy of the scenario using Save as.
Currently, there is no workaround other than to unlock the original scenario manually.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Customer Intelligence Studio | Microsoft® Windows® for x64 | 6.6 | | | |
Microsoft Windows 8 Enterprise 32-bit | 6.6 | | | |
Microsoft Windows 8 Enterprise x64 | 6.6 | | | |
Microsoft Windows 8 Pro 32-bit | 6.6 | | | |
Microsoft Windows 8 Pro x64 | 6.6 | | | |
Microsoft Windows 8.1 Enterprise 32-bit | 6.6 | | | |
Microsoft Windows 8.1 Enterprise x64 | 6.6 | | | |
Microsoft Windows 8.1 Pro 32-bit | 6.6 | | | |
Microsoft Windows 8.1 Pro x64 | 6.6 | | | |
Microsoft Windows 10 | 6.6 | | | |
Microsoft Windows 95/98 | 6.6 | | | |
Microsoft Windows 2000 Advanced Server | 6.6 | | | |
Microsoft Windows 2000 Datacenter Server | 6.6 | | | |
Microsoft Windows 2000 Server | 6.6 | | | |
Microsoft Windows 2000 Professional | 6.6 | | | |
Microsoft Windows NT Workstation | 6.6 | | | |
Microsoft Windows Server 2003 Datacenter Edition | 6.6 | | | |
Microsoft Windows Server 2003 Enterprise Edition | 6.6 | | | |
Microsoft Windows Server 2003 Standard Edition | 6.6 | | | |
Microsoft Windows Server 2003 for x64 | 6.6 | | | |
Microsoft Windows Server 2008 | 6.6 | | | |
Microsoft Windows Server 2008 R2 | 6.6 | | | |
Microsoft Windows Server 2008 for x64 | 6.6 | | | |
Microsoft Windows Server 2012 Datacenter | 6.6 | | | |
Microsoft Windows Server 2012 R2 Datacenter | 6.6 | | | |
Microsoft Windows Server 2012 R2 Std | 6.6 | | | |
Microsoft Windows Server 2012 Std | 6.6 | | | |
Microsoft Windows Server 2016 | 6.6 | | | |
Microsoft Windows Server 2019 | 6.6 | | | |
Microsoft Windows XP Professional | 6.6 | | | |
Windows 7 Enterprise 32 bit | 6.6 | | | |
Windows 7 Enterprise x64 | 6.6 | | | |
Windows 7 Home Premium 32 bit | 6.6 | | | |
Windows 7 Home Premium x64 | 6.6 | | | |
Windows 7 Professional 32 bit | 6.6 | | | |
Windows 7 Professional x64 | 6.6 | | | |
Windows 7 Ultimate 32 bit | 6.6 | | | |
Windows 7 Ultimate x64 | 6.6 | | | |
Windows Millennium Edition (Me) | 6.6 | | | |
Windows Vista | 6.6 | | | |
Windows Vista for x64 | 6.6 | | | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2021-05-26 16:33:51 |
Date Created: | 2021-03-30 07:34:26 |