You can use macro variables to generate text strings in the output filenames of the Communication and Export nodes within a SAS Customer Intelligence Selection campaign (for example, test_&COMMCD._&CAMPCD..csv).

Within a Selection campaign that has two or more Communication nodes, when the export parameters in all Communication nodes are set to Replace and the export filenames include macro variables (as described above), the export files are created as expected when the campaign is executed the first time. However, when the campaign is subsequently executed, although one of the export files is overwritten (as expected), the output data from the other Communication nodes are appended to the existing export files instead of the export files that are being replaced.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Marketing Automation	Windows 7 Professional 32 bit	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Windows 7 Home Premium x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows Server 2008	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows Server 2003 for x64	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2003 Standard Edition	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2003 Enterprise Edition	6.1_M1		9.3 TS1M2
		Microsoft Windows 8.1 Enterprise 32-bit	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows 8 Pro x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows 8 Pro 32-bit	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows 8 Enterprise x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows 8 Enterprise 32-bit	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft® Windows® for x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Windows 7 Home Premium 32 bit	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Windows 7 Enterprise x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Windows 7 Enterprise 32 bit	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows XP Professional	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2012 Std	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows Server 2012 R2 Std	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows Server 2012 R2 Datacenter	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows Server 2012 Datacenter	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows Server 2008 for x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows Server 2008 R2	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows Server 2003 Datacenter Edition	6.1_M1		9.3 TS1M2
		Microsoft Windows 8.1 Pro 32-bit	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows 8.1 Pro	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Microsoft Windows 8.1 Enterprise x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Windows 7 Professional x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Windows 7 Ultimate 32 bit	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Windows 7 Ultimate x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Windows Vista	6.1_M1		9.3 TS1M2
		Windows Vista for x64	6.1_M1		9.3 TS1M2
		64-bit Enabled AIX	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		64-bit Enabled Solaris	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		HP-UX IPF	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Linux for x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1
		Solaris for x64	6.1_M1	6.3	9.3 TS1M2	9.4 TS1M1

* 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.

---

A fix for this issue for SAS Marketing Automation 6.1_M1 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/K78.html#53823

---

This problem occurs when the export filenames include macro variable names as part of the name.

Type:	Problem Note
Priority:	high

Date Modified:	2014-08-05 12:21:53
Date Created:	2014-08-04 11:47:27