In SAS Marketing Automation, using the operator EXACTLY MATCHES to correlate two fields produces an incorrect result. This problem occurs when custom details are populated by a dynamic list from an Oracle database.

For example, you have two fields, Communication Code and Communication Key, where a single communication code is related to many communication keys. You create two custom details that load dynamic lists from the Oracle database. Then, you create a Communication Key dependent on Communication Code dependencies relationship, using the operator EXACTLY MATCHES. When you select a specific communication code, you should see multiple communication keys in the resulting drop-down list. However, the drop-down list is empty and fails to display any exact matches.

To work around this issue, use the operator CONTAINS instead of EXACTLY MATCHES.

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

After you apply the hot fix, enable the following Java option:

To enable the Java argument in Microsoft Windows operating environments (where servers are started as Windows services):

1. Navigate to the server location where the sas.wip.services.war file is located. That location is, typically, SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer1_1\sas_webapps.
2. Navigate to the SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer1_1\conf directory and open the wrapper.conf file.
3. Add the new argument to the wrapper.conf file, as shown below:
   
   wrapper.java.additional.XX=-Dcom.sas.prompts.trimvalues=true
   In this argument, XX represents the next number in the sequence that already exists in the file. For the new argument, modify XX to be the next number in that sequence.

To enable the option in Linux or other UNIX operating environments:

1. Navigate to the server location where the sas.wip.services.war file is located. That location is, typically. SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer1_1\sas_webapps.
2. Navigate to the directory that contains the setenv.sh file. This file is typically located in the SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/bin directory.
3. Add the -Dcom.sas.prompts.trimvalues=true option to the setenv.sh file, as shown in the last argument in the following example:
   
   JVM_OPTS="-Xdebug -Xrunjdwp:transport=dt_socket,address=8003,server=y,suspend=n
   -Xmx4096m -Xss256k -Xms1024m
   -XX:PermSize=768m -XX:MaxPermSize=1280m -d64 -XX:NewRatio=8
   -XX:+UseConcMarkSweepGC -XX:+UseTLAB -XX:+DisableExplicitGC
   -XX:+CMSIncrementalMode -XX:+CMSClassUnloadingEnabled -XX:+UseCompressedOops
   -XX:ReservedCodeCacheSize=96m
   -Djava.awt.headless=true -Dcom.sas.services.logging.disableRemoteLogging=true
   -Dcom.sas.log.config.ignoreContextClassLoader=true
   -Dsas.svcs.http.max.connections=512 -Dcom.sas.prompts.trimvalues=true"
   
4. After you add the option, restart your system so that the setting takes effect.

Operating System and Release Information

A fix for this issue for SAS Middle Tier 9.4_M3 is available at:

A fix for this issue for SAS Management Console 9.4_M3 is available at:

A fix for this issue for SAS Management Console 9.4_M2 is available at:

A fix for this issue for SAS Middle Tier 9.4_M2 is available at:

A fix for this issue for SAS Middle Tier 9.4_M1 is available at:

A fix for this issue for SAS Management Console 9.4_M1 is available at: