In SAS Marketing Automation, export fields that have a single-value, numeric custom-detail tag are exported as a type NUMERIC instead of type CHARACTER. This behavior can cause problems with the downstream processes that rely on a character field in the export data set. 

Note: Multi-value, numeric custom-detail tags are already exported as character type (for example, "10 10"  or "10,10").

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

Note: After you apply the hot fix, the following new Java argument is introduced  

This new argument (-Dsas.ci.export.numTags.useFieldType=true) enables you to export single-value, numeric custom-detail tags as type NUMERIC.

• Under Windows, add the argument to the wrapper.java.additonal.XX property in the wrapper.conf file, which resides in the SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer6_1\conf directory. 
  wrapper.java.additional.XX=-Dsas.ci.export.numTags.useFieldType=true

  Note: In the wrapper.java.additional.XX property, XX specifies the next number in the sequence that already exists in the file. Modify XX to be the next number in that sequence.



• Under Linux and other UNIX operating environments, add the argument to the JAVA_OPTS= property in the setenv.sh file, which resides in the SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer6_1/bin directory.
  JAVA_OPTS="$JAVA_OPTS -Dsas.ci.export.numTags.useFieldType=true"

  You can add the new argument at the beginning of the JAVA_OPTS= property also, as shown below:

  JVM_OPTS=”-Dsas.ci.export.numTags.useFieldType=true -Xmx1536m -Xss256k -Xms768m

After you add the argument to the appropriate file for your operating system, restart the middle tier so that the settings take effect.

Operating System and Release Information

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