Problem Note 63740: Incorrect counts are shown in some nodes when you use static Link nodes in SAS® Customer Intelligence Studio
In SAS Customer Intelligence Studio, you might see incorrect counts (or example, in Limit, Split ,or Prioritize nodes) when you use static Link nodes in a campaign. This problem happens when you perform steps similar to the following:
- Create a campaign (for example, a campaign called Layer1) that contains a Select node and a Cell node.
- Make the Cell node available for linking and clear the check box for the property Use the most current data when referenced by a link. Then, execute, save, and close the campaign.
- Create another campaign (for example, a campaign called Layer2) that contains a Link node that points to the Cell node in Layer1 and to another Cell node.
- Make the Cell node available for linking and clear the check box for the property Use the most current data when referenced by a link. Then, execute, save, and close the campaign.
- Create a third campaign (Layer3) with a Link node that is linked to the Cell node in Layer2. Then, add the following types of nodes: Limit, Prioritize, or Process. When you execute the campaign in Layer3, the counts are updated properly.
- Change the selection criteria in campaign Layer1. Then, execute and save the campaign, but keep it open.
When you clear and update counts for Layer3, the Limit node calculates a certain percentage (for example, 10%) of the counts from Layer1, but it does not calculate counts from Layer2. The same issue occurs with the Split and Prioritize nodes, as demonstrated in the following example:
The Link node still contains the counts from Layer2, as expected.
The incorrect behavior is introduced when you have enabled the following Java arguments:
-Dcom.sas.ci.alwaysrunlinknode=true
-Dcom.sas.ci.alwaysrunlinknode.cis.latest=true
-Dcom.sas.ci.staticlinknode.owntable=true
To work around this issue, save and close all three Layer campaigns. Then, when you clear and update counts for Layer3, the counts are correct.
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.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8 Enterprise 32-bit | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8 Enterprise x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8 Pro 32-bit | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8 Pro x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8.1 Enterprise 32-bit | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8.1 Enterprise x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8.1 Pro 32-bit | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8.1 Pro x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 10 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2008 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2008 R2 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2008 for x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2012 Datacenter | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2012 R2 Datacenter | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2012 R2 Std | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2012 Std | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2016 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2019 | 6.5 | 6.6 | | 9.4 TS1M6 |
Windows 7 Enterprise 32 bit | 6.5 | 6.6 | | 9.4 TS1M6 |
Windows 7 Enterprise x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Windows 7 Home Premium 32 bit | 6.5 | 6.6 | | 9.4 TS1M6 |
Windows 7 Home Premium x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Windows 7 Professional 32 bit | 6.5 | 6.6 | | 9.4 TS1M6 |
Windows 7 Professional x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Windows 7 Ultimate 32 bit | 6.5 | 6.6 | | 9.4 TS1M6 |
Windows 7 Ultimate x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
64-bit Enabled AIX | 6.5 | 6.6 | | 9.4 TS1M6 |
64-bit Enabled Solaris | 6.5 | 6.6 | | 9.4 TS1M6 |
HP-UX IPF | 6.5 | 6.6 | | 9.4 TS1M6 |
Linux for x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Solaris for x64 | 6.5 | 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-04-02 12:41:10 |
Date Created: | 2019-02-26 06:05:42 |