Problem Note 59908: Holdout names are incorrect in Communication nodes after you change the A/B Test node type
 |  |  |  |  |
After you change the type of an A/B Test node (with holdouts enabled) from Champion/Challenger to Challenger/Challenger and you connect the new output cells to the same communication, the holdout name and code in the Communication node is incorrect.
For example, suppose that you have a campaign with an A/B Test node that contains a champion cell CHAMP1 and a challenger cell CHALL1, as shown below:
In this case, the holdout name in the communication will be CHAMP1_Control, with a holdout code of CGCHAPMP1.
Then, you change the A/B test node type to Challenger/Challenger with cell codes of CHALL1 and CHALL2.
If you then reconnect the output cells to the communication, the communication holdout name and code remain incorrect as CHAMP1_Control and CGCHAPMP1 rather than Chall-A_Control and CGCHALLA, as shown below.
To work around this issue, delete the A/B Test node and then re-create it.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Customer Intelligence Studio | Microsoft® Windows® for x64 | 6.3 | 6.4 | 9.4 TS1M2 | |
| Microsoft Windows 8 Enterprise 32-bit | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Microsoft Windows 8 Enterprise x64 | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Microsoft Windows 8 Pro 32-bit | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Microsoft Windows 8 Pro x64 | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Microsoft Windows 8.1 Enterprise 32-bit | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Microsoft Windows 8.1 Enterprise x64 | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Microsoft Windows 8.1 Pro 32-bit | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Microsoft Windows 8.1 Pro x64 | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Microsoft Windows 10 | 6.3 | 6.4 | 9.4 TS1M2 | |||
| 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.4 | 9.4 TS1M2 | |||
| Microsoft Windows Server 2008 R2 | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Microsoft Windows Server 2008 for x64 | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Microsoft Windows Server 2012 Datacenter | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Microsoft Windows Server 2012 R2 Datacenter | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Microsoft Windows Server 2012 R2 Std | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Microsoft Windows Server 2012 Std | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Microsoft Windows XP Professional | 6.3 | |||||
| Windows 7 Enterprise 32 bit | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Windows 7 Enterprise x64 | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Windows 7 Home Premium 32 bit | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Windows 7 Home Premium x64 | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Windows 7 Professional 32 bit | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Windows 7 Professional x64 | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Windows 7 Ultimate 32 bit | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Windows 7 Ultimate x64 | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Windows Millennium Edition (Me) | 6.3 | |||||
| Windows Vista | 6.3 | |||||
| Windows Vista for x64 | 6.3 | |||||
| 64-bit Enabled AIX | 6.3 | 6.4 | 9.4 TS1M2 | |||
| 64-bit Enabled Solaris | 6.3 | 6.4 | 9.4 TS1M2 | |||
| HP-UX IPF | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Linux for x64 | 6.3 | 6.4 | 9.4 TS1M2 | |||
| Solaris for x64 | 6.3 | 6.4 | 9.4 TS1M2 | |||