Campaign | partitions | partition[n] | server | dataProcessing

The longNumericIdsAsText property specifies whether the Campaign macro language will treat numeric IDs longer than 15 digits as text. This property affects ID fields. It has no effect on non-ID fields. This property is useful if you have numeric ID fields with more than 15 digits AND you want to include ID values in criteria.

• Set the value to TRUE to specify that numeric IDs longer than 15 digits will be treated as text.
• When the value is FALSE, numeric IDs longer than 15 digits are treated as numeric values (and thus might lose precision or uniqueness if truncated or rounded). If you do anything that treats the ID values as numeric (such as profiling, or using in a Derived Field), the text is converted to numeric, and precision beyond the 15th digit is lost.

This setting is ignored if the partitions > partition[n] > dataSources > [data_source_name] > ForceNumeric property is set to TRUE for fields coming from this data source.

FALSE

TRUE | FALSE

The stringConcatWithNullIsNull property controls the behavior of the Campaign macro STRING_CONCAT.

When the value is TRUE, STRING_CONCAT returns NULL if any of its inputs is NULL.

When the value is FALSE, STRING_CONCAT returns the concatenation of all of its non-NULL properties; in this case, STRING_CONCAT returns NULL only if all of its inputs are NULL.

TRUE

TRUE | FALSE

The performCaseInsensitiveComparisonAs property specifies how Campaign compares data values when the compareCaseSensitive property is set to no (that is, during case-insensitive comparisons). This property is ignored if the value of compareCaseSensitive is yes.

When the value is UPPER, Campaign converts all data to upper case before comparing.

When the value is LOWER, Campaign converts all data to lower case before comparing.

LOWER

UPPER | LOWER

The upperAllowsDate property specifies whether the UPPER database function allows a DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the Campaign server.

Set the value to TRUE if the database is SQL Server or Oracle. The UPPER function in these databases allows a DATE/DATETIME parameter.

Set the value to FALSE if the database is DB2® or Teradata. The UPPER function in these databases does not allow a DATE/DATETIME parameter.

Note that this setting is global, not per data source. If a value of no is recommended for any data source in use, set the value to no. If a value of yes is recommended for all data sources in use, set the value to yes.

TRUE

TRUE | FALSE

The compareCaseSensitive property specifies whether the Campaign data comparisons are sensitive to alphabetic case (UPPER vs. lower).

When the value is FALSE, Campaign ignores case differences when comparing data values and sorts textual data in a binary, case-insensitive manner. This setting is strongly recommended when English data is used.

When the value is TRUE, Campaign distinguishes data values based on case differences, performing a true binary-value comparison of each character. This setting is strongly recommended when non-English data is used.

FALSE

TRUE | FALSE

The lowerAllowsDate property specifies whether the LOWER database function allows a DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the Campaign server.

Set the value to TRUE if the database is SQL Server or Oracle. The LOWER function in these databases allows a DATE/DATETIME parameter.

Set the value to FALSE if the database is DB2 or Teradata. The LOWER function in these databases does not allow a DATE/DATETIME parameter.

Note that this setting is global, not per data source. If a value of no is recommended for any data source in use, set the value to no. If a value of yes is recommended for all data sources in use, set the value to yes. Typically, only one database type is in use at a customer site, but there are some installations in which multiple database types are in use.

TRUE

TRUE | FALSE

The substrAllowsDate property specifies whether the SUBSTR/SUBSTRING database function allows a DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the Campaign server.

Set the value to TRUE if the database is Oracle or Teradata. The SUBSTR/SUBSTRING function in these databases allows a DATE/DATETIME parameter.

Set the value to FALSE if the database is SQL Server or DB2. The SUBSTR/SUBSTRING function in these databases does not allow a DATE/DATETIME parameter.

Note that this setting is global, not per data source. If a value of no is recommended for any data source in use, set the value to no. If a value of yes is recommended for all data sources in use, set the value to yes.

TRUE

TRUE | FALSE

The ltrimAllowsDate property specifies whether the LTRIM database function allows a DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the Campaign server.

Set the value to TRUE if the database is SQL Server, Oracle, or Teradata. The LTRIM function in these databases allows a DATE/DATETIME parameter.

Set the value to FALSE if the database is DB2. The LTRIM function in this database does not allow a DATE/DATETIME parameter.

Note that this setting is global, not per data source. If a value of no is recommended for any data source in use, set the value to no. If a value of yes is recommended for all data sources in use, set the value to yes. Typically, only one database type is in use at a customer site, but there are some installations in which multiple database types are in use.

TRUE

TRUE | FALSE

The rtrimAllowsDate property specifies whether the RTRIM database function allows a DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the Campaign server.

Set the value to TRUE if the database is SQL Server, Oracle, or Teradata. The RTRIM function in these databases allows a DATE/DATETIME parameter.

Set the value to FALSE if the database is DB2. The RTRIM function in this database does not allow a DATE/DATETIME parameter.

Note that this setting is global, not per data source. If a value of no is recommended for any data source in use, set the value to no. If a value of yes is recommended for all data sources in use, set the value to yes.

TRUE

TRUE | FALSE

The likeAllowsDate property specifies whether the LIKE database function allows a DATE/DATETIME parameter, and therefore whether the operation may be performed in the database or must be performed by the Campaign server.

Set the value to TRUE if the database is SQL Server or Oracle. The LIKE function in these databases allows a DATE/DATETIME parameter.

Set the value to FALSE if the database is DB2 or Teradata. The LIKE function in these databases does not allow a DATE/DATETIME parameter.

TRUE

TRUE | FALSE

The fileAllSpacesIsNull property controls how Campaign interprets an empty field in a mapped flat file by specifying whether an all-spaces value in a flat file should be considered to be a NULL value.

When the value is TRUE, an all-spaces value is considered to be a NULL value. Campaign matches queries such as <field> is null, but fails queries such as <field> = "".

When the value is FALSE, an all-spaces value is treated as a non-NULL empty string. Campaign matches queries such as <field> = "", but fails <field> is null.

TRUE

TRUE | FALSE