Problem Note 14219: Marketing Automation export fails with incorrect Subject Id when there
are duplicate labels in the Information Map
SAS Marketing Automation Campaign Studio export nodes may fail when
exporting if the Information Map contains the same label and/or
description value for fields in different folders.
SAS Marketing Automation searches the Information Map using the fields
description and then processes the underlying database field
accordingly. If duplicate descriptions exist then an incorrect database
field may be returned causing an error similar to the one below in the
Stored Processes log:
MPRINT(MAEXPVAL): proc sort data=MATables.TQNOWCPNSLUNNCAABSASDemoUser
out=readyToExport nodupkey;
MPRINT(MAEXPVAL): by PLP_ID;
ERROR: Variable PLP_ID not found.
MPRINT(MAEXPVAL): run;
ERROR: No BY statement used or no BY variables specified. A BY statement
must be used with variable names to sort on.
NOTE: The SAS System stopped processing this step because of errors.
WARNING: The data set WORK.READYTOEXPORT may be incomplete. When this
step was stopped there were 0 observations and 0 variables.
A fix for this issue is available at:
http://www.sas.com/techsup/download/hotfix/ma42.html#014219
Operating System and Release Information
SAS System | SAS Campaign Studio | Microsoft Windows Server 2003 Standard Edition | 4.2 | 4.3 | 9.1 TS1M3 | 9.1 TS1M3 SP3 |
Microsoft Windows XP Professional | 4.2 | 4.3 | 9.1 TS1M3 | 9.1 TS1M3 SP3 |
Microsoft Windows Server 2003 Enterprise Edition | 4.2 | 4.3 | 9.1 TS1M3 | 9.1 TS1M3 SP3 |
Microsoft Windows Server 2003 Datacenter Edition | 4.2 | 4.3 | 9.1 TS1M3 | 9.1 TS1M3 SP3 |
Microsoft Windows 2000 Server | 4.2 | 4.3 | 9.1 TS1M3 | 9.1 TS1M3 SP3 |
Microsoft Windows 2000 Advanced Server | 4.2 | 4.3 | 9.1 TS1M3 | 9.1 TS1M3 SP3 |
Microsoft Windows 2000 Datacenter Server | 4.2 | 4.3 | 9.1 TS1M3 | 9.1 TS1M3 SP3 |
Microsoft Windows 2000 Professional | 4.2 | 4.3 | 9.1 TS1M3 | 9.1 TS1M3 SP3 |
*
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:54:24 |
Date Created: | 2005-01-18 09:31:16 |