Selection Overview
CGX provides the ability to select which contact records you wish to export.

#1a & #1b (Left & Right brackets)
CGX allows for embedded conditions which require matching left and right brackets (shown as "(, ((, ), ))". These are optional and generally not required for simple selections. You should be familiar with the construction of multi-tiered conditional statements.
#2 - Field Selection
You can select any field shown in the Outlook field list (standard & custom) including keyword fields (i.e. categories). Fields do not need to be selected for export in order to be used in the selection process.
#3 - Selection Operators
There are 18 possible selection criteria operators that can be used however not all operators will be valid with all field types. A message will be displayed if an invalid operator is selected for the type of field it is being compared to.
Description of operators are as follows:
| ▪ | = - "equal to" |
| ▪ | <> - "not equal to" |
| ▪ | < - "less than" |
| ▪ | <= - "less then or equal to" |
| ▪ | > - "greater than" |
| ▪ | >= - "equal to or greater then" |
| ▪ | Is Blank / Not Is Blank |
These operators will select any record where the field contains either an "empty string" OR the field is NULL which are two completely separate internal values. The reason that these are combined for the <Blank> operator is that from a user interface perspective, there is no visible difference when looking at fields that are either "empty" or contain a "null" value and in most cases (or no way of knowing from a practical standpoint). The desired result in most cases is to select records in these cases that do not have any kind of value in the field.
In order to select only fields that are "empty" and NOT NULL, a separate IS NOT NULL condition simply needs to be added
to the overall selection criteria.
| ▪ | Is Null / Not Is Null |
This is similar to the Blank operators except that this will ONLY select fields that contain (or not contain) NULL values.
| ▪ | Contains / Not Contains / Begins w/ (w=with) / Ends w/ |
These operators are essentially shorthand versions of the IS LIKE and NOT IS LIKE operators included for convenience. When using "Contains", any record found to have the value specified anywhere in it's value will be selected. When using keyword fields which have multiple values separated by a "," (comma), there should be a single condition line added for each value you wish to have included.
Example of a complete "Catgories" field = "Business,Real Estate,Industrial"
If you wanted to select all contacts that contained the "Real Estate" and "Industrial" keywords, you would create two conditions for the same field using AND/OR for each single keyword value.
| ▪ | Between / Not Between / Is Like / Not Is Like |
For a detail overview of these operators - see "Like & Between Operators"
#4 - Field Values
Field values will be validated based on the field type and operator selected for the condition. Some simple rules that will be enforced are:
| ▪ | Only numeric values are allowed for currency/numeric fields |
| ▪ | No value can be entered for the <Blank> or <Null> operators |
| ▪ | Valid positive boolean values allowed are (case insensitive): |
"Y", "YES", "T", "TR", "TRUE", "ON", "1"
and will be automatically replaced with "-1"
| ▪ | Valid negative boolean values allowed are (case insensitive): |
"N", "NO", "F", "FA", "FALSE", "OFF", "0"
and will be automatically replaced with = "0"
There is no need to enter bracketing "quote marks" for text fields. These will be automatically added as required.
#5 - AND/OR
Whenever multiple conditions are entered, an AND/OR selection must be added to the condition. When multiple conditions can be ambiguous, you should use the LB/RB (Left & right brackets). For example:
A condition set of:
field1 = value1 OR
field2 = value2 AND
field3 = value3
will not produce the same results if created as follows:
field1 = value1 OR
(field2 = value2 AND
field3 = value3)
In the second example, records would only be selected if the condition for <field1> was true OR the combined conditions for <field2> AND <field3> were true.