To map a base record table to an existing delimited file

To make data accessible to flowchart processes, you can map a new base record table to an existing delimited file. You can map the table when you edit a flowchart or use the Campaign Settings page.

The delimited file must be located on the Campaign server within your partition (that is, the file must be located under your partition root).

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

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

Select Map to Existing File, then click Next.

For File Type, select Delimited File.

In the Settings section, check First Row of Data Contains Field Names if you want to automatically use the first row of data to define the fields of the base table.

You can override these values later.

Select a Field Delimiter to indicate which character separates each field in a row of data: TAB, COMMA, or SPACE.

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

This setting is important if you have a space-delimited file with spaces in field entries. For example, if you have a row of data such as: "John Smith" "100 Main Street", set the Field Delimiter to Space and set the Qualifier to Double Quote so the 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.

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

Define the fields for the new table:

Use the Add and Remove buttons to specify which Source Table Fields to include in the new table. By default, all fields in the file are listed.

Use the Up 1 and Down 1 buttons to adjust field order. Click the Field Name column in the New Table Fields section to automatically sort column names alphabetically in ascending (or descending) order.

You can adjust the field type (Numeric or Text) and width, which are automatically detected based on the numRowsReadToParseDelimitedFile configuration setting. For example, if IDs are detected to be 2 characters wide, but you know that IDs can consist of up to 5 characters, increase the value to 5.

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

10.

When finished, click Next.

The Specify table name and field information screen opens.

11.

Accept the defaults, or edit the IBM® Campaign Table Name field to change the name of the table as it will appear in Campaign. You can also change the IBM® Campaign Field Name mapped to each source field name by selecting the field name and editing the text in the IBM® Campaign 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 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, 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.

Click Add.

The Audience Level and ID Fields window opens.

Select an Audience Level Name.

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

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.

Repeat steps a through e 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 manage through the table manager.