SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 63740: Incorrect counts are shown in some nodes when you use static Link nodes in SAS® Customer Intelligence Studio

DetailsHotfixAboutRate It

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:

  1. Create a campaign (for example, a campaign called Layer1) that contains a Select node and a Cell node.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Customer Intelligence StudioMicrosoft® Windows® for x646.56.69.4 TS1M6
Microsoft Windows 8 Enterprise 32-bit6.56.69.4 TS1M6
Microsoft Windows 8 Enterprise x646.56.69.4 TS1M6
Microsoft Windows 8 Pro 32-bit6.56.69.4 TS1M6
Microsoft Windows 8 Pro x646.56.69.4 TS1M6
Microsoft Windows 8.1 Enterprise 32-bit6.56.69.4 TS1M6
Microsoft Windows 8.1 Enterprise x646.56.69.4 TS1M6
Microsoft Windows 8.1 Pro 32-bit6.56.69.4 TS1M6
Microsoft Windows 8.1 Pro x646.56.69.4 TS1M6
Microsoft Windows 106.56.69.4 TS1M6
Microsoft Windows Server 20086.56.69.4 TS1M6
Microsoft Windows Server 2008 R26.56.69.4 TS1M6
Microsoft Windows Server 2008 for x646.56.69.4 TS1M6
Microsoft Windows Server 2012 Datacenter6.56.69.4 TS1M6
Microsoft Windows Server 2012 R2 Datacenter6.56.69.4 TS1M6
Microsoft Windows Server 2012 R2 Std6.56.69.4 TS1M6
Microsoft Windows Server 2012 Std6.56.69.4 TS1M6
Microsoft Windows Server 20166.56.69.4 TS1M6
Microsoft Windows Server 20196.56.69.4 TS1M6
Windows 7 Enterprise 32 bit6.56.69.4 TS1M6
Windows 7 Enterprise x646.56.69.4 TS1M6
Windows 7 Home Premium 32 bit6.56.69.4 TS1M6
Windows 7 Home Premium x646.56.69.4 TS1M6
Windows 7 Professional 32 bit6.56.69.4 TS1M6
Windows 7 Professional x646.56.69.4 TS1M6
Windows 7 Ultimate 32 bit6.56.69.4 TS1M6
Windows 7 Ultimate x646.56.69.4 TS1M6
64-bit Enabled AIX6.56.69.4 TS1M6
64-bit Enabled Solaris6.56.69.4 TS1M6
HP-UX IPF6.56.69.4 TS1M6
Linux for x646.56.69.4 TS1M6
Solaris for x646.56.69.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.