Problem Note 53394: Common Data Model tables do not update correctly when a campaign execution fails to publish in SAS® Customer Intelligence Studio
If a campaign execution fails to publish in SAS Customer Intelligence Studio, new rows are not added to the Common Data Model tables CI_COMMUNICATION or CI_CELL_PACKAGE after the next successful campaign execution.
The problem occurs in a scenario similar to the following:
- You create a campaign by selecting Cell ► Communication ► Process (Process node). The campaign should look similar to the following:
Note: In this image, Select is a node.
- Then you execute the campaign.
At this point an entry is made in the table that shows a value of 1 for COMMUNICATION_OCCURRENCE_NO.
-
The Process node fails, which causes the campaign execution to fail as well. When that happens, two entries then appear in the CI_CELL_PACKAGE and CI_COMMUNICATION tables. The tables have COMMUNICATION_OCCURRENCE_NO values of 1 and 2, and a COMMUNICATION_STATUS_CD value of _11.
In order for the campaign to execute successfully, you need to modify the Process node again.
At this point, a third entry should be added to the tables that shows a value of 3 for COMMUNICATION_OCCURRENCE_NO. However, no such entry is added to the tables. The campaign is flagged to indicate that the publish is completed for every execution, but the flag is not reset when an error occurs.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Marketing Automation | Microsoft® Windows® for x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows 8 Enterprise x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows 8 Pro x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows 8.1 Enterprise 32-bit | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows 8.1 Enterprise x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows 8.1 Pro | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows 8.1 Pro 32-bit | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows Server 2008 R2 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows Server 2008 for x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows Server 2012 Datacenter | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows Server 2012 R2 Datacenter | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows Server 2012 R2 Std | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows Server 2012 Std | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Windows 7 Enterprise x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Windows 7 Professional x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
64-bit Enabled AIX | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
64-bit Enabled Solaris | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
HP-UX IPF | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Linux for x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Solaris for x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
*
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: | 2014-07-18 15:12:30 |
Date Created: | 2014-07-03 06:09:15 |