The Extract process

Use the Extract process to select fields from one table and write them out to another table for subsequent processing. The Extract process is designed to pare down a large amount of data to a manageable size for subsequent operations, resulting in vast performance improvements.

The Extract process can take input from a cell, single table, strategic segment, optimized list (Unica Optimize only), or Unica Deliver landing page (Unica Deliver only). If you select a strategic segment as input, you must join it to a table before you can extract fields.

If you use several Extract processes in a series, only the fields in the final Extract process are written out.

If you use several Extract processes in parallel (in different branches in the same flowchart), they behave the same as persistent derived fields:
  • The extracted fields attach to the inbound cell
  • The extracted fields are calculated before query execution in that process
  • Multiple extracted fields are available in subsequent processes
  • When extracted fields are sent to a contact process:
    • If an extracted field is not defined for a cell, its value = NULL
    • If a single ID is in more than one cell, one row is output for each cell
  • When extracted fields are sent to a Segment or Decision process, the extracted field must exist in all selected input cells for it to be used in segmenting by query.

Extracted tables

Data is extracted as either a binary file on the Unica Campaign server or as a table with a UAC_EX prefix.

Extract tables are not deleted at the end of a flowchart run. An extract table persists so that users can continue to access it to perform operations such as profiling its fields.

An extract table is deleted only when you delete its associated Extract process, flowchart, campaign, or session.

Extract process now supports mapping to a dimension table (ENH08531).

The Extract process now allows adding existing dimension tables to the extract table. The extract table becomes a base table for the selected dimension table and can be used in downstream processes. Use the new Dimension tab in the Extract configuration dialog to select a dimension and the key fields to join on.

User cannot map a Base table from DS1 and specify its dimension table from DS2. User cannot specify base-dimension relationship between 2 tables if they are from different datasources. Hence, even if a table can be individually mapped as Base/Dimension tables, they cannot be used as Base and Dimension of each other in any of process boxes except when used in Extract box. The Extract tab allows to JOIN Base table from DS1 with Dimension Table from DS2. This functionality is limited to Extract box only.

User can map base table from DS1 and user can map an Individual dimension table from DS2. Here one cannot specify Base dimension relationship.
Note: Dimension table from DS2 can be made available on Extract box > Extract tab, so that it can be used as dimension table of a base table, even though they are from different datasources.
Note: To conserve space, system administrators can periodically delete tables with a UAC_EX prefix. However, if these tables are removed, you must rerun the affected Extract processes before you rerun flowcharts or profile fields in the now-missing tables. Otherwise, Unica Campaign generates "Table Not Found" errors.
Steps to configure Dimension tab
  1. Add a flowchart. Add Extract box .
  2. Click on Admin > Tables and map a Database table Table1 with audience level Customer(numeric) , from a datasource say - DS1 pointing to ORACLE database.
  3. Map a Dimension table "Dim1" with Key Field of Numeric type from another datasource say - DS2 pointing to SQLSERVER database.
  4. Configure EXTRACT1PB with input table from Oracle database DS1.
  5. Extract fields to SQLServer database DS2.
  6. Select Dimension table "Dim1" available on Dimension tab and select numeric field from New Table's Key Field(s) To Use dropdown.