To map a base record table to an existing delimited file

You can map a new base record table to an existing file on the Campaign server within your partition (that is, the file must be located under your partition root) when editing a flowchart or through the Campaign Settings page.

You map a new base record table to make data accessible to processes in flowcharts.

1.	Begin from the New Table Definition - Select the table type window.

2.	If necessary, select Base Record Table, then click Next.

3.	Select Map to Existing File, then click Next.

4.	Select Delimited File for the File Type.

5.	In the Settings section of the window, check First Row of Data Contains Field Names if this is the case.

This automatically uses the first row of data to define the fields of the base table. You can override these values later.

6.	Select the Field Delimiter (this is the character used to separate each field in a row of data): TAB, COMMA, or SPACE.

7.	Select the Qualifier used to indicate how strings are delimited in the file: None, Single Quote, or Double Quote.

This is important if you have a space-delimited file with spaces as part of a field entry. In this case, the field must be enclosed in quotation marks so the embedded spaces are not interpreted as field delimiters. For example, if you had a row of data such as: “John Smith” “100 Main St.”, with the delimiter as SPACE and Qualifier set to NONE, Campaign would parse this as five different fields (“John” as the value of the first field, “Smith” as the second, “100” as the third, and so forth). If the qualifier is set to Double Quote, then this record is correctly parsed as two fields (name and street address).

Campaign does not support the use of the double quote character (") in field entries of delimited files. If any of your field entries contain double quotes, change them to another character before mapping a table to the file.

8.	Click Browse to select the Source File from within your partition directory.

9.	Specify the fields to use in the new table. By default, all fields in the file are listed.

If you are mapping a delimited file, the first 50 lines of the file will be sampled for field type and width. You can override the field type (Numeric or Text) and the width, which are automatically detected. For example, if the IDs in the first 50 lines are detected to be 2 characters wide, but you know that IDs later in the file consist of up to 5 characters, increase the value to 5.

If the width value is too small, an error may occur.

You use the Add, Remove, Up 1 and Down 1 buttons to specify the Source Table Fields that are included in the new table and their order. Click on the Field Name column in the New Table Fields section to automatically sort column names alphabetically in ascending (or descending) order.

10.	When finished, click Next.

The Specify table name and field information screen opens.

11.

Accept the defaults, or edit the Unica Table Name field to change the name of the table as it will appear in Campaign. You can also change the Unica® Field Name mapped to each source field name by selecting the field name and editing the text in the Unica Field Name text box in the Edit Selected Field Information section.

12.	When your changes are complete, click Next.

The Specify the selected table's audience level and assign ID field(s) to it screen opens.

13.	Select an Audience Level from the drop-down list. The Audience Fields list is automatically populated. You must select a field in the new base table that is the corresponding key for each listed entry.

14.	Click Next.

The Specify Additional Audience Levels screen opens.

15.

Optionally, in the Specify Additional audience levels screen, you can specify one or more additional audience levels contained in the base record table. Adding additional audience levels allows users to use this table as a “switching table” to translate from one audience level to another using the Audience process in a flowchart.

a.	Click Add.

The Audience Level and ID Fields window opens.

b.	Select an Audience Level Name.

c.	For each Audience Field, match appropriate field(s) from the base table to the corresponding key(s) in the audience level.

d.	If the selected audience level is normalized (that is, each unique audience ID appears at most once in the current base table), check This audience level is normalized in this table.

Click OK.

f.	Repeat steps a through f for each audience level you want to add for the base table, then click Next.

16.	You can choose to pre-compute the distinct values and frequency counts for specific fields, or allow users to perform real-time profiling of data in the base record table.

17.	Click Finish.

You have created the base record table based on an existing file. The new base table is part of the current table catalog, which you can managed through the table manager.