Problem Note 57788: All nodes in a diagram might disappear in SAS® Customer Intelligence Studio when you delete a selection-dependent group
 |  |  |  |  |
You might encounter an issue that all nodes in a diagram might disappear in SAS Customer Intelligence Studio when you delete a selection-dependent group. At the same time, the following error message is shown in the SASCustIntelCore6.x.log file:
2016-01-26 09:17:45,633 ERROR [CIAsyncExec-9] [xxx2e89349f2062c:xx98374:1527cead29d:-34ab] [sasdemo] com.sas.analytics.crm.util.SystemCheck - Error getting root node.
java.lang.NullPointerException
at com.sas.analytics.crm.util.client.PromptHelper.getDisplayablePromptValuesMap(PromptHelper.java:2323)
at com.sas.analytics.crm.flow.MACodeNode.getNodeAttributeList(MACodeNode.java:1235)
at com.sas.analytics.crm.flow.CINode.getNodeDOForUI(CINode.java:320)
at com.sas.analytics.crm.flow.FlowLinkedDOBuilder.FillInLinks(FlowLinkedDOBuilder.java:98)
at com.sas.analytics.crm.flow.FlowLinkedDOBuilder.FillInLinks
...
at com.sas.analytics.crm.flow.CIFlow.getLinkedNodeRecursive(CIFlow.java:3867)
at com.sas.analytics.crm.flow.CIFlow.getRootNode(CIFlow.java:3857)
at com.sas.analytics.crm.flow.ejb.FlowBean.getRootNode(FlowBean.java:902)
at com.sas.analytics.crm.flow.client.FlowDelegate.getRootNode(FlowDelegate.java:241)
at com.sas.analytics.crm.flow.ejb.FlowProxyImpl$11.call(FlowProxyImpl.java:377)
at com.sas.analytics.crm.flow.ejb.FlowProxyImpl$11.call(FlowProxyImpl.java:371)
at com.sas.analytics.crm.cm.ejb.util.WrappedRunnable.run(WrappedRunnable.java:74)
at com.sas.analytics.crm.ejb.SessionCountingRunnableQueue$QueueHandler.run(SessionCountingRunnableQueue.java:83)
at com.sas.analytics.crm.task.ejb.ClearedThreadLocalRunnable.run(ClearedThreadLocalRunnable.java:17)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1121)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
at java.lang.Thread.run(Thread.java:780)
This issue is introduced when you use selection-dependent groups in a Process node or a Custom Diagram Tool node and you delete the selection-dependent group accidentally.
As a workaround, you can use the SAS® Marketing Automation Integration Utilities, as follows:
- Extract the campaign. Note: This extraction works, but it generates warnings that various nodes cannot be found.
- Import the extracted XML file with a new filename. The campaign loads warnings and the errant nodes are missing, but the rest of the campaign loads successfully and the nodes are visible.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Note: This hot fix does not fix the problem with the Process node, but the campaign does not lose all of the nodes.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Customer Intelligence Studio | Microsoft® Windows® for x64 | 6.3 | 6.5 | 9.4 TS1M3 | |
| Microsoft Windows 8 Enterprise 32-bit | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Microsoft Windows 8 Enterprise x64 | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Microsoft Windows 8 Pro 32-bit | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Microsoft Windows 8 Pro x64 | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Microsoft Windows 8.1 Enterprise 32-bit | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Microsoft Windows 8.1 Enterprise x64 | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Microsoft Windows 8.1 Pro | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Microsoft Windows 8.1 Pro 32-bit | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Microsoft Windows 10 | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Microsoft Windows Server 2008 | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Microsoft Windows Server 2008 R2 | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Microsoft Windows Server 2008 for x64 | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Microsoft Windows Server 2012 Datacenter | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Microsoft Windows Server 2012 R2 Datacenter | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Microsoft Windows Server 2012 R2 Std | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Microsoft Windows Server 2012 Std | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Windows 7 Enterprise 32 bit | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Windows 7 Enterprise x64 | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Windows 7 Home Premium 32 bit | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Windows 7 Home Premium x64 | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Windows 7 Professional 32 bit | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Windows 7 Professional x64 | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Windows 7 Ultimate 32 bit | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Windows 7 Ultimate x64 | 6.3 | 6.5 | 9.4 TS1M3 | |||
| 64-bit Enabled AIX | 6.3 | 6.5 | 9.4 TS1M3 | |||
| 64-bit Enabled Solaris | 6.3 | 6.5 | 9.4 TS1M3 | |||
| HP-UX IPF | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Linux for x64 | 6.3 | 6.5 | 9.4 TS1M3 | |||
| Solaris for x64 | 6.3 | 6.5 | 9.4 TS1M3 | |||
A fix for this issue for SAS Marketing Automation 6.3 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/R60.html#57788| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2016-10-31 15:59:54 |
| Date Created: | 2016-03-04 04:40:26 |