Custom drop-down lists disappear when you try to transfer a campaign to SAS Customer Intelligence from SAS Marketing Operations Management. This problem occurs when you have a campaign template in SAS Marketing Operations Management that has pre-defined lists with customer detail fields and you try to transfer the campaign to SAS Customer Intelligence. The lists disappear, and you see only static text fields.

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

After the application of this hot fix (SAS^® Marketing Automation 6.1_M1, Hot Fix K78014) or a later hot fix to an existing 6.1_M1 deployment only, you need to download new JAR files manually. These new JAR files are required in order to resolve the issue that is reported in this note as well as in the following SAS Notes:

• SAS Note 58372, "The count might be incorrect when you use SAS^® web services to modify a SAS^® Customer Intelligence Studio 'Select' node"
• SAS Note 58487, "SAS^® Marketing Automation custom date fields show the date input as two days earlier when the date is updated via SAS^® web services"

After you apply the hot fix, contact SAS Technical Support and download one of the following two files, as directed by SAS Technical Support, depending on your web application server type.

• For JBoss deployments, use this file: d3cintr3K78014jb.zip
• For IBM WebSphere and Oracle WebLogic deployments, use this file: d3cintr3K78014ws.zip

For all web-application servers, make a backup copy of the sas.analytics.crm.webservices.integration.ear file and save it to another location (for example, C:\backupcopy).

Perform the following steps for whichever file you download.

For JBoss deployments:

1. Using WinZip or a similar tool, unzip the downloaded file, d3cintr3K78014jb.zip to a new folder (for example, C:\newjars).
2. Stop the JBoss application server in the location where the sas.analytics.crm.webservices.integration.ear file is deployed (for example, ...\web-server-installation--directory\SASServer6\deploy_sas\sas.analytics.crm.webservices.integration.ear).
3. Search your JBoss deployment folder where the sas.analytics.crm.webservices.integration.ear file is deployed (for example, ...\jboss-eap-5.2\jboss-as\server\SASServer6) for a tmp folder that contains at least the folders deploy and aopdynclasses. Delete the entire contents of this tmp folder.
4. Delete all files from the \lib folder that resides in a location similar to ...\web-server-installation-directory\SASServer6\deploy_sas\sas.analytics.crm.webservices.integration.ear\sas.analytics.crm.webservices.integration.war\WEB-INF.
5. Copy all files from the new folder that you created in step one (for example, C:\newjars) to the lib folder that resides in ...\web-server-installation-directory\SASServer6\deploy_sas\sas.analytics.crm.webservices.integration.ear\sas.analytics.crm.webservices.integration.war\WEB-INF\.
6. Re-start your JBoss web-application server.

For WebLogic and WebSphere deployments:

1. Using WinZip or a similar tool, unzip d3cintr3K78014ws.zip to a new folder (for example, C:\newjars).
2. Remove the sas.analytics.crm.webservices.integration.ear file.
3. Unzip the original sas.analytics.crm.webservices.integration.ear file.
4. Similarly, unzip the original sas.analytics.crm.webservices.integration.war file.
5. Delete all files from the \lib folder that resides in a location similar to ...\web-server-installation-directory\SASServer6\deploy_sas\sas.analytics.crm.webservices.integration.ear\sas.analytics.crm.webservices.integration.war\WEB-INF.
6. Copy all files from the new folder that you created in step 1 (for example, C:\newjars) to the \lib folder that resides in a location similar to ...\web-server-installation-directory\SASServer6\deploy_sas\sas.analytics.crm.webservices.integration.ear\sas.analytics.crm.webservices.integration.war\WEB-INF\.
7. Re-zip the sas.analytics.crm.webservices.integration.war file.
8. Re-zip the sas.analytics.crm.webservices.integration.ear file.
9. Re-deploy the sas.analytics.crm.webservices.integration.ear.

Operating System and Release Information

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

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

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