Usage Note 41827: The Export file might not contain the expected data if you do not use the Refine Output option
When you run a campaign or diagram in SAS® Customer Intelligence Studio and your data mart contains duplicate subject IDs, the data in the subsequent Export file might not be what you expect.
Consider this simple scenario:
- A single table (Customer) with two columns and two rows:
Customer Id (Subject Id) Gender
1000 F
1000 M
- A simple diagram: Select Node (Select where GENDER='M'#41; ► Cell Node ► Export Node (with both Customer Id and Gender fields selected to be output).
- When the diagram is executed, the temporary table from the Cell Node will contain a single row and column:
- When you run the Export node and you select the check box Discard rows with duplicate subject Ids (it is selected by default), only the first row is processed. This is true even though multiple rows are retrieved from the Customer table because you selected to discard duplicates. The first row contains a GENDER='F'. Therfore, the application writes this value to the Export file. This behavior occurs even though you originally selected GENDER='M' in the Select node and you expect that a row with a gender value of M will be written to the Export file.
However, if you need to export the value or values that you previously selected in the upstream Select node, then you can use the Refine Output option in the following way:
- In the Export node, click the Refine Output button. This button opens the Refine Output window.
- In the Refine Output window, select the check box next to the Select node. Then click OK.
This Refine Output functionally only works correctly if you refine output on the Select node. If you refine output on the Cell node, the Refine Output functionality has no effect because the Cell node only contains one row. As a result, the application retrieves only the first first row from the Customer table.
Operating System and Release Information
| SAS System | SAS Customer Intelligence Studio | Microsoft® Windows® for x64 | | |
| Microsoft Windows 95/98 | | |
| Microsoft Windows 2000 Advanced Server | | |
| Microsoft Windows 2000 Datacenter Server | | |
| Microsoft Windows 2000 Server | | |
| Microsoft Windows 2000 Professional | | |
| Microsoft Windows NT Workstation | | |
| Microsoft Windows Server 2003 Datacenter Edition | | |
| Microsoft Windows Server 2003 Enterprise Edition | | |
| Microsoft Windows Server 2003 Standard Edition | | |
| Microsoft Windows Server 2003 for x64 | | |
| Microsoft Windows Server 2008 | | |
| Microsoft Windows Server 2008 for x64 | | |
| Microsoft Windows XP Professional | | |
| Windows 7 Enterprise 32 bit | | |
| Windows 7 Enterprise x64 | | |
| Windows 7 Home Premium 32 bit | | |
| Windows 7 Home Premium x64 | | |
| Windows 7 Professional 32 bit | | |
| Windows 7 Professional x64 | | |
| Windows 7 Ultimate 32 bit | | |
| Windows 7 Ultimate x64 | | |
| Windows Millennium Edition (Me) | | |
| Windows Vista | | |
| Windows Vista for x64 | | |
*
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.
If your data mart contains duplicate Subject IDs, the data in the subsequent Export file might not be as you expect. This is not a design flaw.
| Date Modified: | 2011-02-02 08:22:14 |
| Date Created: | 2010-12-10 08:21:24 |
