Problem Note 34331: Historical contents for user-defined fields are overwritten in the SAS® Customer Intelligence Common Data Model when a campaign is published manually
 |  |  |  |  |
SAS® Marketing Automation enables you to attach user-defined fields to campaigns and communications. These fields are then published to the SAS Customer Intelligence Common Data Model (CDM), either when the campaigns are executed or when the user manually publishes a campaign from SAS® Customer Intelligence Studio.
If you change the contents of the user-defined fields between each subsequent execution of the campaign, then these changes are correctly published to the CDM. However, if you manually publish a campaign, then all of the historic values that are in the CDM for the user-defined fields will be overwritten by the current values.
For example, you have a communication with a user-defined field named Reference that has an initial value of REF01. When you execute the campaign, the CDM value for the user-defined field is set to REF01.
You then change the value to REF02 and execute the campaign. Now there are two values in the CDM (one for each execution): REF01 and REF02.
You change the value again to REF03 and manually publish the campaign. Now, there are three values in the CDM, one for each occurrence, but the values are all set to REF03. The values REF01 and REF02 are overwritten.
There is no workaround for this issue other than to avoid manually publishing campaigns if the values for the user-defined fields change.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Note: This issue has been hot fixed in SAS Marketing Automation 5.1. In SAS Marketing Automation 5.3 you need to apply the hot fix to SAS Marketing Automation 5.3M3.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Marketing Automation | 64-bit Enabled AIX | 5.1 | 5.4 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Windows Vista | 5.1 | 5.4 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| Windows Vista for x64 | 5.1 | 5.4 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| Microsoft Windows XP Professional | 5.1 | 5.4 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| Microsoft Windows Server 2003 Standard Edition | 5.1 | 5.4 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 5.1 | 5.4 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| Microsoft Windows Server 2003 Datacenter Edition | 5.1 | 5.4 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| Microsoft Windows NT Workstation | 5.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows 2000 Server | 5.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows 2000 Professional | 5.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows 2000 Datacenter Server | 5.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows 2000 Advanced Server | 5.1 | 9.1 TS1M3 SP4 | ||||
| Linux | 5.1 | 5.4 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| HP-UX IPF | 5.1 | 5.4 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| 64-bit Enabled Solaris | 5.1 | 5.4 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| 64-bit Enabled HP-UX | 5.1 | 5.4 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 5.1 | 5.4 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 5.1 | 5.4 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| Microsoft Windows XP 64-bit Edition | 5.1 | 5.4 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 5.1 | 5.4 | 9.1 TS1M3 SP4 | 9.2 TS2M0 | ||