See AlsoAn Import Configuration comprises information about the source and type of data to be imported, the base Object to be created as a result of the import, and details about the mapping of the data to relevant Properties of the resultant Talisma Object. Using the Talisma Data Management Utility, you can create an Import Configuration and execute it to import data.
Creating an Import Configuration comprises creating and executing an SSIS package. While creating an Import Configuration, you can choose to create a fresh import Configuration or use an existing SSIS package to import data.
The Create Import Configuration wizard guides you through the process of creating an Import Configuration. The process includes the following steps:
Step 1: Specifying Basic Information
Specify the name of the Import Configuration and the Talisma Object that must be used as the base Object. You can choose to configure data transfer afresh or use an existing SSIS package.
The Talisma Object for which items must be created when data is imported must be defined as the base Object for the Import Configuration. For example, if the data to be imported comprises names and e-mail addresses, you can select Contact as the base Object. Contact items will then be created in Talisma.
Step 2: Specifying Source File Information
• If you are creating a fresh Import Configuration, specify the location of the source file on Page 2. You must also select the format of the data and the type of Talisma data that must be created when the data is imported.
• If you are using an existing SSIS package, specify the name of the SSIS package that must be used to import data and the type of Talisma data to be created.
Step 3: Defining the Mode of Data Import
Select the mode in which you want to run the data import. Depending on the selected mode, data will be imported and added as new Object items or Properties of existing Object items will be updated.
Map columns of the interface table to Object Properties in Talisma. The list of Talisma Properties displayed depends on a combination of the base Object and Talisma data type that is selected. Accordingly, the Properties of the Object, RecordList Properties, or related Object Properties will be displayed.
The number of pages in the creation wizard changes depending on the type of data you want to import into Talisma:
• If you are importing items of the base Object only, the number of steps in the wizard is 6.
• If one or more Objects are related to the base Object, you can map the external data to Properties of the related Object in the Talisma Related Object Mapping page. The Related Object Mappings page is displayed after you have specified the Duplicate Check criteria for the base Object. You will then need to specify the related Object mappings, and the Duplicate Check criteria for the related Object. The number of pages in the wizard increases to 9, and the change is indicated in the title bar of the wizard.
• If Relationship Properties of the base Object are being updated, the count of steps in the wizard increases to 9.
Step 5: Specifying Duplicate Check Criteria
Select the Talisma Property to be used to check for duplicate records.
Step 6: Creating Reference Mappings
Specify the values to be used for the User and Team Properties for the selected columns of the data that you are importing.
• If you are importing an Interaction or Interaction Events, you can specify mappings for the medium through which the Interaction is created.
• If you are importing data for Shared Objects, you can specify the Teams with which the Object items must be shared.
|
Note To share Object items with multiple Teams, the Teams value in the source file must be separated by the ± delimiter. For example, Alaska±Ohio. The ± delimiter must be used for the Import New Data, Update Existing Data, and Import and Update Data modes. |
After an Import Configuration is created, you can run it to import data into Talisma. You can also run, modify, or delete an existing Configuration, or view the status of an Import Configuration. You can also view the log of an Import Configuration.
|
Note The Data Import feature synchronizes with SQL Server Integration Services (SSIS) of SQL Server 2008. While you can continue to edit Import Configurations of previous versions that were associated with Data Transformation Services (DTS) packages, you can associate any new Import Configurations that you create only with SSIS packages. |
The following table summarizes the pages that are displayed when you create an Import Configuration:
|
Operation |
Pages That Are Displayed |
| Creating a default Import Configuration |
Pages 1 through 6 of the Talisma Data Management Utility. For information about the pages, see the topics Step 1 – Specifying Basic Information through Step 6 – Creating Reference Mappings. Note The layout of the Step 2 page differs based on the selection of one of the following options in the Step 1 page: • Use Existing SSIS Package: The Talisma Create Import Configuration – Step 2 of 6 page is displayed. • Configure Data Transfer: The Talisma Create Import Configuration – Step 2 page is displayed. For more information about these pages, see Step 2 - Specifying Source File Information. |
| Creating an Import configuration of the base Object and other Object with which the base Object shares a Many to One or One to One Relationship |
The following pages are displayed: • Pages 1 through 4 of the Import wizard. See the topics Step 1 – Specifying Basic Information through Step 6 – Creating Mappings. Note The functionality of importing related Objects is available only if you select the value Regular in the Type of Talisma Data list in the Create Import Configuration – Step 2 page of the Import wizard • On page 4, when you click Related Object Configuration, perform the import of the related Object in pages 4.1 through 4.3. See Creating and Updating Related Objects in an Import Operation. Note Pages 4.1 to 4.3 that are specific to related Objects are similar to pages 4 through 6 that are specific to the base Object. • Pages 4 through 6 of the Import wizard. See the topics Step 4 – Creating Mappings through Step 6 – Creating Reference Mappings. For a complete description of the steps to perform this operation, see Creating and Updating Related Objects in an Import Operation. |
| Updating Relationship Properties |
The Import creation wizard includes 9 pages: • Page 1: Select the Configure Data Transfer option. See Step 1 – Specifying Basic Information. • Page 2: Select a Many to Many relationship in the Type of Talisma Data list. See Step 2 – Specifying Source File Information. • Page 3: The Import New Data option is selected by default. The Update Existing Data and Import and Update Data options are disabled. See Step 3 – Defining the Mode of Data Import. • Pages 4 and 5: Map the relationship Properties of the related Object in step 4 and create the duplicate check criteria for them in step 5. See Step 4 – Creating Mappings and Step 5 – Specifying Duplicate Check Criteria. • Pages 6 and 7: Map the relationship Properties of the base Object in step 6 and create the duplicate check criteria for them in step 7. See Step 4 – Creating Mappings and Step 5 – Specifying Duplicate Check Criteria. • Page 8: Map columns in the interface table to common relationship Properties. See step 3 in Updating Relationship Properties. • Page 9: Create reference mappings. See Step 6 – Creating Reference Mappings. For a complete description of the steps to perform this operation, see Updating Relationship Properties. |
To Log on to the Talisma Data Management Utility
1. Double-click the Talisma Data Management Utility icon on the desktop or click Talisma Data Management Utility from the Talisma Data Management Utility group in the Windows Start menu.
The Talisma Data Management Utility - Login page is displayed.
2. Specify the Login Name, and Password, and the details of the Server and database.
3. Click Login.
The main menu of the Talisma Data Management Utility is displayed.
|
Note If a value is not specified in the Password field, the windows login credentials are used to log on to the Talisma Data Management Utility. |