Data Maps are used when bringing data into your Engage+ database. The Data Map defines the sequence of the columns in the import file, and identifies the correct table and field into which each column should be loaded. Also, if the destination table is joined to other tables, the Data Map can be used to load the inbound data into the desired fields in the joined tables.
Data Maps can be defined as either a reusable asset, or as a one time asset that gets built "on the fly" when defining a Manual Import. For the most part, the functionality between reusable and one-time Data Maps is the same. However, one key difference between the two options is that a reusable Data Map allows you to derive and populate a Calculated Field; this functionality is not available when defining a one-time Data Map.
The Data Map screen is also used to manage Data Maps used for the platform's Load and Send feature. Load and Send allows you to import "campaign-ready" files containing all the information needed to build and deploy the Campaign (such as personalization fields, and contact information like Email Address). This data is loaded into a special table dedicated specifically to the Load and Send feature, rather than into the regular relational database tables. The Data Map controls where the data from the campaign-ready file is loaded. Data Maps that are intended for use in Load and Send Campaigns differ slightly from regular Data Maps, as follows:
The only valid Data Processing option is "Create Only."
Certain Advanced Options aren't supported.
Calculated Fields and Soft Matches aren't supported.
The Data Maps screen is accessible by the following method:
From the Main menu, select Data > Integration > Data Maps
Create a New Reusable Data Map Data Maps can be defined as either a reusable asset, or as a one time-only asset that gets built "on the fly" when defining a Manual Import. To create a new reusable Data Map:
Note: You can never modify this Source Table after the Data Map is created.
Note: If you selected a Load and Send table above in step 3, the Data Processing drop-down menu is disabled, with "Create Only" selected. For a Load and Send Data Map, this is the only valid option.
Note: If you selected "Fixed Width" from the "File Delimiter" drop-down menu, the system adds "Start" and "Length" text fields so you can enter the starting and ending positions of each field in the import file. As you add more fields, the system automatically increments the "Col #" value by one, but you can optionally enter a different value here, if needed. If you need to ignore a column in the import file, simply skip over that column number in the sequence. For example, if you want to ignore column #4 in your import file, the numbering sequence in your Data Map would go from Column #3 to Column #5, and leave out column #4. The important point to keep in mind is that the sequence you're defining here represents the column order from the input file, and the mapped field you select is the location in the database where that data is being inserted. You can also use negative values as the "Col #" in order to negatively map fields. When you negatively map a field, you're telling the system that you want to populate the specified "Map to" field in the database, but that you don't expect this value to be present in the import file. Instead, the value is going to come from some place other than the import file, such as a SQL script, for example. The Data Map must include the field (or fields) that make up the Unique Identifier for the Source Table, even if you're not actually intending to import the Unique Identifier field. The user interface performs a validation on the Data Map that requires the Unique ID field (or fields) be present in the Data Map. If you're not actually providing the Unique ID value in the import file, you'll need to use the Soft Match feature (described below). In this situation, select the Unique ID field from the "Map to" drop-down menu, and enter a negative number for the column number. In this manner, the Unique ID is present in the Data Map (allowing you get past the screen validation), but you don't actually have to provide any values for it, and it won't interfere with the columns that you are importing.
Note: If you run a Calculated Field as part of an import process, the system derives and populates that field only for the records in the import file. Conversely, if you set up a Calculated Field schedule, the system derives and populates the field for every record in the table (see Tables for more details). Note: If you selected a Load and Send table above in step 3, the Calculated Fields option is not available.
If the import file doesn't contain the Unique Identifier field for the Source Table, then you must use the Soft Match feature in order to successfully load the data. The Soft Match lets you match to the database using any fields with a Data Type of "Email," "Phone," "Twitter," "Facebook ID," or "Push Registration ID." For example, let's say the Unique ID on your "Recipient" table is "Member ID," but you don't have Member ID data available in your import file. You could instead select some other field, such as "Email Address," that contains unique data, and match on that instead. If the soft-matched value in the import file matches an existing value in the database, then the platform will make the update to that record in the database. If the soft-matched value does not already exist in the database, the platform creates a "temporary" record. This temporary record can later be merged with a full record that contains the Unique Identifier. As described above, if you're using the Soft Match feature, you still must add the Unique Identifier field (or fields) to the Data Map, even if you're not actually intending on providing the Unique ID fields on the inbound data. The Unique ID must be part of the Data Map in order to save the Data Map.
Note: If you selected a Load and Send table above in step 3, the Soft Match feature is not available.
|
Copy a Data Map To copy an existing item to use as the basis for a new item:
|
View or Edit a Data Map To view or edit a Data Map:
|
Delete a Data Map To delete an item:
Foldered items are moved to the Recycle Bin. Non-foldered items are permanently deleted.
|