Behavior of the Lead Object in an Update Scenario

Lead records in Talisma are updated through an Import operation based on the following criteria:

•   Lead records in Talisma will be updated through an Import operation only if values mapped to the Campus Property of the Lead are available in the data source. If the value for the Campus Property is not available, the update of Lead records will fail and the No Matches Found message will be logged in the Import error log.

•   The Talisma Data Management Utility will check if the value of the following fields of the identified Lead is set to No:

◦   Duplicate

◦   Invalid

◦   Disqualified

The update operation of the Lead record will fail if one or more of the Properties has the value Yes. In this scenario, the No Matches Found message will be logged in the Import error log.

The Lead update operation does not apply to invalid Leads.

To create invalid Leads by running an Import Configuration, set the value of the CreateLeadasInvalid option in the Talisma Global Config Utility to 1.

Note 

•   In a scenario where multiple Leads are available in Talisma that match with the Lead record that is available in the data source, the value specified for the UpdateOneWhenMultipleMatches parameter in the Talisma Global Config Utility will determine which Lead record will be updated.

The UpdateOneWhenMultipleMatches parameter can have one of the following values:

◦   1 - The Import operation will update the oldest record that occurs in Talisma Main Database if multiple matches are available.

◦   0 - Duplicate information will not be imported into Talisma, and the following error message is displayed in the Import error log: Multiple Matches Found.

For information about the behavior of the UpdateOneWhenMultipleMatches parameter for Objects other than the Lead Object, see “Configuring Settings for the Import Configuration ”.

•   The update of Lead records will fail in the following scenarios, and the No Matches Found error will be logged in the Import error log:

◦   When the value mapped to the Campus Property of the Lead is changed in the data source.

◦   When the value of the Property based on which a duplicate check will be performed is changed in the data source.

◦   If details of a Lead whose Disqualified, or Invalid Property is Yes are available in Talisma Main Database.

◦   If the value mapped to the Campus Property is not available in the data source.

 

Note 

Related Objects of the Lead can be updated in the Lead record if the ID of the related Object is specified in the data source.

Example 1

When a Lead record is created through an Import operation, the ID of the MBA Program Object item can be specified in the data source and mapped to the Program Property of the Lead. When the Import operation is performed, the value MBA is updated in the Program Property of the newly created Lead.

Example 2

When the Lead record that is created in Example 1 is updated through an Import operation, the MBA Program Property that was set in the Lead can be changed to Arts by specifying the ID of the Arts Program Object item in place of the ID of the MBA Program Object item in the data source. When the Import operation is performed, the value MBA is changed to Arts in the Program Property of the Lead.

In both scenarios, this functionality can be achieved if the MBA and Arts Program Object items were available in Talisma before the Lead is created through the Import operation.