| Legal Information |
|
You can filter your Outlook data using the Filter= directive, which should appear as a separate line at the beginning of the CLIPFORM template. The Filter= directive is written in the following format:
[Filter=OutlookField=Value]Where OutlookField is any valid Outlook field, and Value is the value to be filtered. You may use any of the following logical operators: =, <>, >, <, <=, and >=. The following are examples of acceptable filters:
[Filter=CreationTime > 01/01/2001]You can specify dates relative to today's date. For example, Today-1 filters on yesterday; Today+1 filters on tomorrow; and Today+10 filters on ten days from now. Here's an example which uses two filters to filter a task list to include only tasks that are not yet complete, and are due within the next 7 days:
[Filter=WebPage <> '']
[Filter=AllDayEvent = True]
[Filter=Complete=False]Note, you can filter on user properties. This is a convenient way to manage a mailing list which is a subset of a contact database. For example, to create a mailing list for a newsletter, you could add an Outlook custom yes/no field titled Newsletter. Display this custom field in an Outlook folder view, and simply check this value for the contacts you wish to add to this list. Then use CLIPFORM to extract only the contact names and addresses on this mailing list:
[Filter=DueDate<=Today+7]
[Source=outlook:Contacts]You can also filter on Outlook fields containing enumerations. However, you must use the integer value Outlook assigns to each enumerated field. These integer values are shown below.
[Output=c:\docs\newslist.txt]
[Filter=Newsletter=True]
[FullName]
[BusinessAddress]
[Filter=Status<>2]
Beginning in version 1.2, you can include multiple filter criteria in the same Filter= directive, linking them with a logical AND (items are only selected if they meet all criteria) or logical OR (items are selected if they meet either criterion). Separate filter criteria with a vertical bar (|) for logical OR. Separate filter criteria with a caret (^) for logical AND. For example, the following filter will extract all persons born before 1960 or after 1990 (logical OR):
[Filter=Birthday<1/1/1960|Birthday>=1/1/1990]The following filter will extract all persons born between 1960 and 1970 (logical AND):
[Filter=Birthday<1/1/60|Birthday>1/1/80^Birthday<1/1/90]You can also use more than one Filter= directive. Note, if you use more than one Filter= directive, items are only selected if they meet ALL filter criteria (logical AND). Include
A variation of filters is the Include= directive. Unlike the Filter= directive, the Include= directive will include any item which meets any of two or more filters on the same field. For example, the following template will include only individuals who were born during the 1950's:
[Source=outlook:Contacts]This version, however, uses the Include= directive to include individuals born before 1930 or after 1990:
[Output=c:\docs\output.txt]
[Filter=Birthday>=1/1/1950]
[Filter=Birthday<1/1/1960]
[Sort=Birthday]
[FullName] [Birthday|mmmm d, yyyy]
[Source=outlook:Contacts]
[Output=c:\docs\output.txt]
[Include=Birthday<1/1/1930]
[Include=Birthday>=1/1/1990]
[Sort=Birthday]
[FullName] [Birthday|mmmm d, yyyy]
Note, if you tried to use the Filter= directive instead of the Include= directive, no items would be returned, as no items would have a Birthday that was both on or after 1/1/1990 and before 1/1/1930.
IMPORTANT NOTE: The Include= directive is slower than the Filter= directive, since it must tag all Outlook items meeting any of the Include criteria. It should not be used in conjunction with the Filter= directive, since results can be unpredictable. Most of the time you will want to use the Filter= directive in your templates, for its speed and flexibility. However, the Include= directive leaves each found item tagged with the user property ClipFormTemp=True. You can therefore create a view in Outlook filtered to show only items with this value û thus allowing ClipForm to indirectly let you create a filtered view in Outlook with OR logic.
| Search Knowledge Base | Feedback |