Problem Note 62736: Incorrect treatment assignments are published when you manually publish in SAS® Customer Intelligence Studio
In SAS Customer Intelligence Studio, the COMMUNICATION_OCCURRENCE_NO column (in the CI_COMMUNICATION table) is incorrectly assigned to a treatment and is published to the SAS® Customer Intelligence Common Data Model. This problem happens when you perform steps similar to the following:
- Create two treatments: Treatment A and Treatment B.
- Create a campaign and add the two treatments as shown below:
- Assign Treatment A to the Cell node, as shown here:
- Execute the campaign. The COMMUNICATION_OCCURRENCE_NO column, which displays a value of 1, is published with the correct Treatment A:
- Next, manually publish the campaign in SAS Customer Intelligence Studio.
- Change from Treatment A to Treatment B and execute the campaign. With this step, the COMMUNICATION_OCCURRENCE_NO column with a value of 2 is published. However, both Treatment A and Treatment B are assigned to the same occurrence number.
When you execute the campaign, it shows the correct Treatment B for the COMMUNICATION_OCCURRENCE_NO column that has a value of 3. However, the incorrect Treatment A from the manual publishing process is still displayed for the COMMUNICATION_OCCURRENCE_NO column that has a value of 2.
As long as you execute the campaign for which treatments are correctly assigned, the problem does not occur. However, when you switch from publishing the campaign manually (via the Publish campaign button) to an execution step, the treatments are no longer properly assigned to the occurrence number. As a result, you cannot identify which treatment is currently assigned to the campaign.
To work around this problem, do not manually publish inside SAS Customer Intelligence Studio when you change a treatment assignment.
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.6 | | 9.4 TS1M6 |
Microsoft Windows 8 Enterprise 32-bit | 6.3 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8 Enterprise x64 | 6.3 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8 Pro 32-bit | 6.3 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8 Pro x64 | 6.3 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8.1 Enterprise 32-bit | 6.3 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8.1 Enterprise x64 | 6.3 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8.1 Pro 32-bit | 6.3 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8.1 Pro x64 | 6.3 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 10 | 6.3 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2008 | 6.3 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2008 R2 | 6.3 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2008 for x64 | 6.3 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2012 Datacenter | 6.3 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2012 R2 Datacenter | 6.3 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2012 R2 Std | 6.3 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2012 Std | 6.3 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2016 | 6.3 | 6.6 | | 9.4 TS1M6 |
Windows 7 Enterprise 32 bit | 6.3 | 6.6 | | 9.4 TS1M6 |
Windows 7 Enterprise x64 | 6.3 | 6.6 | | 9.4 TS1M6 |
Windows 7 Home Premium 32 bit | 6.3 | 6.6 | | 9.4 TS1M6 |
Windows 7 Home Premium x64 | 6.3 | 6.6 | | 9.4 TS1M6 |
Windows 7 Professional 32 bit | 6.3 | 6.6 | | 9.4 TS1M6 |
Windows 7 Professional x64 | 6.3 | 6.6 | | 9.4 TS1M6 |
Windows 7 Ultimate 32 bit | 6.3 | 6.6 | | 9.4 TS1M6 |
Windows 7 Ultimate x64 | 6.3 | 6.6 | | 9.4 TS1M6 |
64-bit Enabled AIX | 6.3 | 6.6 | | 9.4 TS1M6 |
64-bit Enabled Solaris | 6.3 | 6.6 | | 9.4 TS1M6 |
HP-UX IPF | 6.3 | 6.6 | | 9.4 TS1M6 |
Linux for x64 | 6.3 | 6.6 | | 9.4 TS1M6 |
Solaris for x64 | 6.3 | 6.6 | | 9.4 TS1M6 |
*
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: | 2019-08-29 15:59:40 |
Date Created: | 2018-08-10 07:14:07 |