Problem Note 59912: Communication holdout code is blank after you copy and paste a flow that contains an A/B Test node
When you use auto-generated codes and you copy and paste a flow containing an A/B Test node with the holdout control group feature enabled, the holdout code in the pasted communication is blank.
The original flow and the Holdouts tab of in the Communication Properties dialog box looks similar to the following:
Then, when you copy and paste the original flow, the newly created flow is similar to this image:
To work around this issue, open and save the A/B Test node in the pasted flow.
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.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 8 Enterprise 32-bit | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 8 Enterprise x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 8 Pro 32-bit | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 8 Pro x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 8.1 Enterprise 32-bit | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 8.1 Enterprise x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 8.1 Pro 32-bit | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 8.1 Pro x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 10 | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 95/98 | 6.3 | | | |
Microsoft Windows 2000 Advanced Server | 6.3 | | | |
Microsoft Windows 2000 Datacenter Server | 6.3 | | | |
Microsoft Windows 2000 Server | 6.3 | | | |
Microsoft Windows 2000 Professional | 6.3 | | | |
Microsoft Windows NT Workstation | 6.3 | | | |
Microsoft Windows Server 2003 Datacenter Edition | 6.3 | | | |
Microsoft Windows Server 2003 Enterprise Edition | 6.3 | | | |
Microsoft Windows Server 2003 Standard Edition | 6.3 | | | |
Microsoft Windows Server 2003 for x64 | 6.3 | | | |
Microsoft Windows Server 2008 | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows Server 2008 R2 | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows Server 2008 for x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows Server 2012 Datacenter | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows Server 2012 R2 Datacenter | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows Server 2012 R2 Std | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows Server 2012 Std | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows XP Professional | 6.3 | | | |
Windows 7 Enterprise 32 bit | 6.3 | 6.5 | | 9.4 TS1M3 |
Windows 7 Enterprise x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Windows 7 Home Premium 32 bit | 6.3 | 6.5 | | 9.4 TS1M3 |
Windows 7 Home Premium x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Windows 7 Professional 32 bit | 6.3 | 6.5 | | 9.4 TS1M3 |
Windows 7 Professional x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Windows 7 Ultimate 32 bit | 6.3 | 6.5 | | 9.4 TS1M3 |
Windows 7 Ultimate x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Windows Millennium Edition (Me) | 6.3 | | | |
Windows Vista | 6.3 | | | |
Windows Vista for x64 | 6.3 | | | |
64-bit Enabled AIX | 6.3 | 6.5 | | 9.4 TS1M3 |
64-bit Enabled Solaris | 6.3 | 6.5 | | 9.4 TS1M3 |
HP-UX IPF | 6.3 | 6.5 | | 9.4 TS1M3 |
Linux for x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Solaris for x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
*
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: | 2017-04-03 15:58:59 |
Date Created: | 2017-02-07 11:38:56 |