Problem Note 14211: SAS Marketing Automation exports and map nodes may fail when duplicate
variables exist
If an export definition contains duplicated fields, then an error
message is written reporting zero records exported, and in addition the
following errors appear in the remoteservices log:
com.sas.iquery.strategies.sas.oma.relational.SQLGeneration -
Multiple data items used in a business query have the same
resultset ID. All data items used as result items within a
business query must have unique resultset IDs.
The following error will also be seen:
[ERROR] com.sas.analytics.crm.flow.ejb.FlowBean - Async
execution failure
The errors are also possible if selection criteria including a map
node are used to extract data from separate tables that contain
duplicate data item names from the source tables. In this case there
might not be any duplicated names in the export.
A new SAS Marketing Automation custom attribute on the information map
will permit successful use of duplicate names in the source tables by
adding an attribute called OutputColumnName.
The attribute specifies a column name that is to be used in the
internally generated sql in place of the physical column name. This
attribute is available beginning with Hot Fix 2 for SAS Marketing
Automation.
A fix for this issue is available at:
http://www.sas.com/techsup/download/hotfix/ma42.html#014211
Operating System and Release Information
SAS System | SAS Campaign Studio | Microsoft Windows Server 2003 Standard Edition | 4.2 | | 9.1 TS1M3 | |
Microsoft Windows XP Professional | 4.2 | | 9.1 TS1M3 | |
Microsoft Windows Server 2003 Enterprise Edition | 4.2 | | 9.1 TS1M3 | |
Microsoft Windows Server 2003 Datacenter Edition | 4.2 | | 9.1 TS1M3 | |
Microsoft Windows 2000 Server | 4.2 | | 9.1 TS1M3 | |
Microsoft Windows 2000 Advanced Server | 4.2 | | 9.1 TS1M3 | |
Microsoft Windows 2000 Datacenter Server | 4.2 | | 9.1 TS1M3 | |
Microsoft Windows 2000 Professional | 4.2 | | 9.1 TS1M3 | |
*
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: | 2005-03-10 14:56:32 |
Date Created: | 2005-01-17 16:30:30 |