1.
|
Confirm that Campaign is configured properly to access the necessary user tables: See To test user table access.
|
2.
|
3.
|
Save the mapping information in a table catalog for reuse. This way, the table mapping needs to be done only once, and Campaign users who want to include Digital Analytics segments can load the saved catalog to get the mapping information directly. If you want the information to be available for use in all flowcharts, store it in the default catalog (default.cat). See Working with table catalogs.
|
4.
|
Whenever there is a change to the physical table (for example, if columns are added or deleted), you must remap the table. If you do not remap the table, flowcharts using Digital Analytics segments will return an error at run time indicating that the table schema has changed.
|
|
When you map or remap a table, the IBM® Campaign Table Name assigned in the Table Definition wizard must exactly match the TranslationTableName defined in the Campaign configuration settings (see Campaign | partitions | partition[n] | Coremetrics). If you do not edit the table name when using the Table Definition wizard, the names will match.
|
Copyright IBM Corporation 2015. All Rights Reserved.
|