SAS^® Customer Intelligence enables you to move communication definitions between systems by using Import SAS Package and Export SAS Package menu selections in SAS^® Management Console. These selections are available from the Actions list on the Folder tab.

A communication definition might have dependent definitions. If those dependent definitions are not imported with the parent communication definition, problems can occur. One such problem is that exported data might be written to an incorrect location when the communication is run in a campaign. For example, consider the following scenario:

1. You create a SAS Customer Intelligence export definition named ExportDefA. The output from this export process is directed to the directory 'C:\original-path'.
2. You import a communication named CommDefA, which contains the export definition ExportDefA, to the system from another system. However, you do NOT import or replace ExportDefA—a dependency for CommDefA.
3. When CommDefA is imported, you are prompted for an export path for the output and you enter 'C:\my-new-path'.

Because the ExportDefA definition is NOT imported or replaced in this scenario, it still displays the path 'C:\original-path' in the Export Definition plug-in in SAS Management Console. However, when you use CommDefA in a campaign, that communication is exported to 'C:\my-new-path'. The communication definition's export path, which is hidden from users, does not match the path for the export definition. As a result, the data is written to the wrong location.

The only workaround is to open CommDefA in SAS Management Console, remove the export definition from the Exports tab, and then add the export definition again.

Operating System and Release Information