The 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 of the mapping of data to relevant Properties of the resultant Talisma Object. The values of properties can be changed to produce different results when you configure settings for the Import Configuration in the Global Config Utility. This topic describes these properties.
To Configure Settings for the Import Configuration
1. Log on to the Global Config Utility.
The Global Config Utility dialog box is displayed.
The Global Config Utility
2. Select Talisma Data Import from the Module Name list.
3. From the Property List, select a Property and modify it by clicking the Modify Value button.
4. Click Close to complete the modification.
The following table describes default properties for the Data Import module. Values in the Global / Local column must be interpreted as follows:
• Global: Indicates that the property is global and must be modified in the Global Config Utility.
• Local: Indicates that the property is specific to or "local" to the import configuration and its value must be updated in the Data Management Utility. If the value is updated in the Global Config Utility, its changed settings do not affect modifications in the created import configuration.
|
Parameter Name |
Description |
Default Value |
Global / Local |
|
AllowNullEmails |
This parameter determines whether a null email can be imported into Talisma. If the value is 1, a null email can be imported into Talisma. |
0 |
Local |
|
AllowNullRestrictedValues |
This parameter determines whether a null value can be imported into a Property with restricted values in Talisma. If the value is 1, Talisma will allow null values to be imported into the Property. Specifying an invalid value in this parameter produces an incorrect result. |
1 |
Local |
|
DeleteProcessedRecords |
This parameter determines the status of processed records in the staging table of Talisma. If the value is 0, all the records will be retained in the staging table. If the value is 1, all the successfully imported records will be deleted from the staging table. |
0 |
Local |
|
FireRulesContact |
This parameter determines when Contact specific Rules must be triggered in Talisma If the value is set to 1, Contact specific Rules are triggered when a Contact is created as a result of the Import operation. |
0 |
Local |
|
FireRulesOther |
This parameter determines if Rules specific to Objects other than Contacts must be triggered when other operations are performed by the Talisma Data Management Utility. If the value is set to 1, Rules will be triggered when other operations are performed by the Talisma Data Management Utility. Note If the value of the AuditForPropertyUpdate parameter is set to 0, Rules are not triggered even if the value of the FireRulesOther parameter is set to 1. |
0 |
Local |
|
MandateParentPropMapping |
If the value of this parameter is set to 1, the Data Import wizard requires all parent Properties of Dependent Properties to be mapped. |
1 |
Global |
|
ValidateEmail |
If the value of this parameter is set to 1, the Import operation will validate e-mail addresses of Contacts, and Accounts when Contact, and Account information is being imported. |
1 |
Local |
|
AuditForPropertyUpdate |
If the value of this parameter is 1, when the Import operation is performed, Talisma will audit updates to Property values in Talisma. |
0 |
Local |
|
AllowDuplicateEmail |
If the value of this parameter is set to 1, when the Talisma Import operation is performed, a duplicate check is not performed for E-mail type of Properties in the staging table. |
0 |
Local |
|
CreateDTSJobs |
If the value of this parameter is 1, the Import Operation enables individual SQL Server jobs to be created and run for each SSIS package that is configured. The SQL Server job will be created only after the Import operation is performed. Setting the value of this parameter to 1 enables individual SQL Server jobs to be run from the Job Status dialog box. |
0 |
Global |
|
PostProcessing |
If the value of this parameter is set to 1, the Import Configuration wizard enables a single staging table column to be used for post-Import operations. |
0 |
Global |
|
CustomMatchingCriteria |
This parameter is obsolete, and is no longer in use. |
|
Global |
|
UpdateNulls |
If the default value 0 is retained, the new value of the Talisma Property, Null is ignored, and the previous value of the property is retained. If the value of this parameter is set to 1, the new value of the Talisma Property, Null, is retained, and the previous value of the Property is overwritten. |
0 |
Local |
|
BulkImportForRecordList |
If the value of this parameter is 0, a normal Import operation of Recordlist Properties is performed. If the value of this parameter is 1, a Bulk Import operation of Recordlist Properties is performed. If the value of the AuditForPropertyUpdate parameter is set to 1, a normal Import operation is performed regardless of the value set for this parameter. In the value of the NoOfRecordsForBulkImport parameter is set to a specific value, the count of records matching the value that is set will be imported at a time, thus making the Import operation faster. |
0 |
Local |
|
NoOfRecordsForBulkImport |
You can set to the value of this parameter in the range 500 to 500,000. |
500 |
Local |
|
ShowRecordlistPropsForMapping |
If the value of this parameter is 1, RecordList Properties are displayed in the Mappings area, and will be suffixed with the text RL. Only Normal Talisma Properties are displayed in the Mappings area if the value of this parameter is 0. |
0 |
Global |
|
DeleteTransLogsOlderthanDays |
This parameter is used by the JobImp_DeleteFromTransLog SQL Job to delete transaction logs. The JobImp_DeleteFromTransLog SQL Job deletes the transaction logs older than the number of days specified in this parameter. You can change the value of this parameter. |
30 |
Global |
|
AllowCustomReadOnlyPropertyUpdate |
Custom read-only Properties can be imported If the value of this parameter is set to 1. If the value of this parameter is 0, custom read-only Properties can be mapped, but the Talisma Data Management Utility will ignore these mappings and these Properties are not imported. Note All read-only Properties, regardless of their Talisma Global Configurator value, can be mapped to check for duplicates. |
0 |
Local |
|
ImportWhenMultipleMatches |
If the value of this parameter is set to 1, and multiple records with the specified duplicate criteria are available, the most recently created record will be imported, without marking the Import operation as a failure. If the default value 0 is retained, and multiple records with the specified duplicate criteria, are available, the most recently created record is notimported, and the Import operation is marked as a failure. |
0 |
Local |
|
SetDefaultValuesOnCreate |
If you set the value of this parameter is set to 1, default values set for Properties that are not configured to be imported into Talisma will be set based on the values set for these Properties in Talisma Business Administrator. |
0 |
Global |
|
RunSprocsFromOSQL |
If the value of this parameter is set to 1, steps in the jobs specific to the Import operation will be executed using the osql utility. If the value of this parameter is set to 0, steps in the Import operation are executed using database specific jobs. |
1 |
Global |
|
NonUniCodeInteractionText |
If the value of this parameter is set to 1, only non-unicode characters can be imported to Interaction text. A maximum of 7500 characters of Interaction text can be imported. If the value of this parameter is 0, unicode characters can be imported to Interaction text and can have a maximum of 4000 characters. |
0 |
Local |
|
CheckForDuplicatesInStagingTable |
If the value of this parameter is set to 1, a check is made for duplicate entries in the staging table and marks these as errors. If the value of this parameter is set to 0, no check is made for duplicate entries in the staging table. |
1 |
Local |
|
UpdateOneWhenMultipleMatches |
When the value of this parameter is set to 1, the Import operation will update any duplicate record that occurs in Talisma Main Database if multiple matches are available. When the value of this parameter is 0, the duplicate information is not imported into Talisma, and the following error message is displayed: Multiple Matches Found. Note For information about the behavior of this parameter specific to the Lead Object, see “Behavior of the Lead Object in an Update Scenario”. |
0 |
Local |
|
FireRulesManuallyLater |
When the value of this parameter is set to 1, the Import operation updates Talisma Main Database with information about Talisma Rules that must be triggered. To trigger the Rules, run the sprocImp_FlushRuleStack2 stored procedure. It is recommended that you set the value of this parameter to 1 if the count of records to be imported, and the count of Rules is high. This parameter enables you to trigger Rules at a favorable time so that the efficiency of your hardware resources is not compromised. Note You can set the value of this parameter to 1 only if the value of the FireRuleOther parameter is set to 1. |
0 |
Local |
|
FlushRuleStackAfterEveryBatch |
You can set the value of this parameter to 1 only if the value of the FireRuleOther parameter is set to 1. When you do so, Rules are triggered after each record is imported in Talisma. Note Changing the value of this parameter to 1 is recommended only if the count of records to be imported is low. |
0 |
Local |
|
CheckForMandatoryProperties |
If the value of this parameter is set to 1, in addition to importing records that do not contain Mandatory Properties, those records for which values are specified for Mandatory Properties are also imported. If the value of this Property is 0, records are imported into Talisma regardless of whether values are specified for Mandatory Properties. |
1 |
Global |
|
CheckForConditionalMandatoryProperties |
If the value of this parameter is set to 1, in addition to importing records that do not contain Properties with restricted values, those records for which values are specified for Properties with restricted values are also imported. If the value of this Property is 0, records are imported into Talisma regardless of whether values are specified for Properties with restricted values. |
1 |
Global |
|
UseFastForwardCursor |
If the value of this parameter is 0, it enables you to change the image of the cursor. By default, the value of this parameter is 1. |
1 |
Global |
|
AuditWithDirectInserts |
If the value of this parameter is set to 1, audit is enabled for Talisma Properties and events when the Object information is imported into Talisma. By default, the value of this parameter is set to 1. |
1 |
Local |
|
Package DB |
This parameter enables you to specify the name of a database on Talisma Server in which Intermediate tables will be created. If the value of this parameter is Null, the name of Talisma Main Database is automatically updated to this parameter. |
<Main Database> |
Local |
|
AssociateWithOneParentWhenMultipleMatches |
If the value of this parameter is set to 1, multiple parent associations of Talisma Properties are formed with a single parent Property. If the value of this parameter is 0, the Import operation will fail if duplicate Parent Properties are available. |
0 |
Local |
|
CreateLeadasInvalid |
The functionality of the CreateLeadasInvalid parameter can be triggered only if the value of either the CheckForMandatoryProperties, or CheckForConditionalMandatoryProperties parameters is set to 1. If the value of this parameter is 1, Leads are created in Talisma through an import operation even though values for Mandatory, or conditional Mandatory Properties are not specified in the data source. The Invalid Property of the Leads is set to Yes. If the value of this parameter is 0, Leads are not created in the import operation, and the following error message is displayed in the Import log: Mandatory Property is not filled. |
0 |
Global |
|
AssociateRelatedObjectWithDirectUpdate |
This parameter is not used at present. |
Local |
|
|
ImportLeadsInBulkMode |
For information about this parameter, your administrator must contact Professional Services. |
Global |
|
|
UpdateLeadPropertiesInATableCollectively |
If the value of this parameter is set to 1, Lead Properties in a particular table of Talisma Main Database are updated collectively. This reduces the number of requests made to Talisma Main Database while updating Properties. If the value of this parameter is set to 0, Properties of the Lead are updated sequentially. Note When you set the value of this parameter to 1, Rules that must be triggered when related Objects are associated with the Lead will not be triggered during an import operation. If these association Rules need to be triggered, it is recommended that you set the value of this parameter to 0. |
1 |
Global |
The following table describes Lead import operations specific to the CheckForMandatoryProperties and CheckForConditionalMandatoryProperties parameters in the Talisma Global Config Utility:
|
Scenario |
Behavior of the Lead Object |
|
When the value of the CheckForMandatoryProperties and CreateLeadasInvalid parameters is 1. |
|
|
Mandatory Properties are available in the data source. |
Import is successful. Note The Invalid Property of the Lead is set to No. |
|
Mandatory Properties are not available in the data source. |
Import is successful. Note The Invalid Property of the Lead is set to Yes. |
|
When the value of the CheckForMandatoryProperties parameter is 0. |
|
|
Mandatory Properties are available in the data source. |
Import is successful. Note The Invalid Property of the Lead is set to No. |
|
Mandatory Properties are not available in the data source. |
|
|
When the value of the CheckForConditionalMandatoryProperties and CreateLeadasInvalid parameters is 1. |
|
|
Conditional Mandatory Properties are available in the data source. |
Import is successful. Note The Invalid Property of the Lead is set to No. |
|
Conditional Mandatory Properties are not available in the data source. |
Import is successful. Note The Invalid Property of the Lead is set to Yes. |
|
When the value of the CheckForConditionalMandatoryProperties parameter is 0. |
|
|
Conditional Mandatory Properties are available in the data source. |
Import is successful. Note The Invalid Property of the Lead is set to No. |
|
Conditional Mandatory Properties are not available in the data source. |
|
|
Note If you import Lead records into Talisma in a scenario where the value of the CreateLeadasInvalid parameter is set to 0 when the value of one or both of the CheckForMandatoryProperties or CheckForConditionalMandatoryProperties parameters is 1, the import operation fails, and the following message is displayed in the Import log: Mandatory Property is not filled. |