Problem Note 60704: Incorrect counts might appear in an Or node in SAS® Customer Intelligence when the underlying database is Microsoft SQL Server
In SAS Customer Intelligence Studio 6.5, you might receive incorrect counts in an Or node when you add a Link node with a data item that is defined with an expression type of Numeric and a level value of Nominal. This problem happens when you perform steps similar to the following and when the underlying database is Microsoft SQL Server:
- Create a simple diagram by selecting a data item that is defined with an expression type of Numeric and a level value of Nominal. In addition, make the Cell node available for linking, as shown below. Then update counts and save and close the diagram.
- Create a simple diagram with two Select nodes that are linked to an Or node, as shown below. Then update the counts on the Or node.
- Add a Link node. Then select the linkable Cell node that you created in step 1 and add the Link node to the Or node:
- Update the counts on the Or node.
When you finish these steps, the counts from the Link node are missing. In step 4 above, the example still shows only 8,090 counts. It does not add the 11,446 counts from the Link node.
When you update the counts, the SASCustIntelCore6.5.log file shows this error:
2017-06-23 11:32:05,638 ERROR [CIAsyncExec-8] [bcb8a85ab3b6a5b0:1ef4a231:15cd513cd40:-4f77] [sasdemo] alytics.crm.custdata.datapattern.MAQuery - Unable to optimize query: com.sas.analytics.crm.error.client.ApplicationException null
As a workaround, you can add a second Cell node and a second Or node, as shown below:
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 Core Mid-Tier | Solaris for x64 | 6.5 | | | |
Linux for x64 | 6.5 | | | |
HP-UX IPF | 6.5 | | | |
64-bit Enabled Solaris | 6.5 | | | |
64-bit Enabled AIX | 6.5 | | | |
Microsoft® Windows® for x64 | 6.5 | | | |
*
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: | 2017-07-19 11:02:48 |
Date Created: | 2017-06-30 07:12:31 |