SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 50348: A Map node returns incorrect counts if the underlying tables are connected with an outer join

DetailsHotfixAboutRate It

Incorrect counts might be returned when you execute a SAS® Customer Intelligence campaign. This problem occurs if the diagram contains a Map node that is refining its output on data in tables that are connected with an outer join.

For example, you have an information map that has at least two subjects, such as Customer and Accounts.

  1. Each customer may have 1 or many contracts.
  2. Each contract may have 0-many events. The join to the event table must be an outer join to enable selection of customers or contracts with no events.
  3. Create an information map with the following relationship between the underlying tables:
    1. join between Contract and Product_Purchase(Event) a left outer join
    2. join between Product_Purchase and Product a left outer join
Build the campaign based on information map above.
  1. Select all customers with no products.
  2. Connect the Select/Multi-select node to a Map node. Map to Accounts and select Refine.
  3. Specify the refine limit as 1 contract. Specify the refine selection as Product is missing.
  4. Run the Map node. Note that 0 contacts are selected.

When you review the audit log for the Selection node, you see outer joins between Contract and Product_Purchase(Event) and between Product_Purchase(Event) and Product.

The audit log for the Map node reports those same joins as inner joins, which is incorrect and explains the zero count.

There is no workaround.

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 Server 2003 Datacenter Edition5.416.1_M19.3 TS1M29.3 TS1M2
Microsoft® Windows® for x645.416.1_M19.3 TS1M29.3 TS1M2
Microsoft Windows Server 20085.416.1_M19.3 TS1M29.3 TS1M2
Microsoft Windows Server 2003 Enterprise Edition5.416.1_M19.3 TS1M29.3 TS1M2
Microsoft Windows Server 2003 Standard Edition5.416.1_M19.3 TS1M29.3 TS1M2
Microsoft Windows Server 2003 for x645.416.1_M19.3 TS1M29.3 TS1M2
Microsoft Windows Server 2008 R2 for x645.416.1_M19.3 TS1M29.3 TS1M2
Microsoft Windows Server 2008 for x645.416.1_M19.3 TS1M29.3 TS1M2
Microsoft Windows XP Professional5.416.1_M19.3 TS1M29.3 TS1M2
Windows 7 Enterprise 32 bit5.416.1_M19.3 TS1M29.3 TS1M2
Windows 7 Enterprise x645.416.1_M19.3 TS1M29.3 TS1M2
Windows 7 Home Premium 32 bit5.416.1_M19.3 TS1M29.3 TS1M2
Windows 7 Home Premium x645.416.1_M19.3 TS1M29.3 TS1M2
Windows 7 Professional 32 bit5.416.1_M19.3 TS1M29.3 TS1M2
Windows 7 Professional x645.416.1_M19.3 TS1M29.3 TS1M2
Windows 7 Ultimate 32 bit5.416.1_M19.3 TS1M29.3 TS1M2
Windows 7 Ultimate x645.416.1_M19.3 TS1M29.3 TS1M2
Windows Vista5.416.1_M19.3 TS1M29.3 TS1M2
Windows Vista for x645.416.1_M19.3 TS1M29.3 TS1M2
* 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.