SSIS:Global Verify:Output Filter

From Melissa Data Wiki
Revision as of 19:35, 17 October 2014 by Admin (talk | contribs) (Created page with "← SSIS Reference {| class="mw-collapsible" cellspacing="2" style="background-color:#f9f9f9; border:1px solid #aaaaaa; font-size:9pt; color:#0645ad; pa...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

← SSIS Reference

Global Verify Navigation
Advanced Configuration
Melissa Data Cloud
Global Verify Tabs
Pass-Through Columns
Output Filter
Result Codes
Returned Result Codes
Result Codes

SSIS GV OutputFilter.png

The Global Verify Component will output records in up to four streams. The Output Filter tab allows you to control which records go to which stream. Names and usage can be done in any manner. Filters are evaluated from the top down.

Result Codes

The output status of a record is returned via result codes returned by the underlying objects. The Component will combine them into a single, comma-delimited string and write them to the field mapped here. New field names can be created by typing the name into the Output Results Code box.

Output Filter

Select a filter to determine which records will be directed to a particular output stream. A custom filter may be created based on individual need, each pin filters the records in a cascading effect, where the results code is compared against the first expression (Pin 1) and then compared against Pin 2, and so on.

No Filter
All records are written to a single output stream.
Pre-built Filter
The Component comes with a pre-built filter for a common application:
  1. Fully Verified DeliveryPoint Addresses Only ([AV24] and [AV25])
  2. Fully Verified Addresses Only ([AV2*])
  3. Partially Verified Address or Better ([AV*])
  4. Partially Verified Addresses Only ([AV1*])
Custom Filter
Records matching the filter will be directed to the designated file.
For more information, see Custom Output Filters below.

Custom Output Filters

Custom rules are an advanced subject. You should be comfortable with Boolean operations before using custom rules in a production environment.

For more information see Custom Output Filters.