Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Cloud MDM - Customer 360 for Salesforce
  3. Configuring the Data Cleansing Settings
  4. Managing Batch Jobs
  5. Verifying Addresses, Email Addresses, and Phone Numbers
  6. Synchronizing Salesforce Records with CC360
  7. Managing Duplicate Records
  8. Consolidating Records
  9. Converting External Records to Salesforce Records
  10. Managing Hierarchies
  11. Integrating Cloud MDM - Customer 360 for Salesforce with Multidomain MDM
  12. Managing Multi-Org
  13. Troubleshooting
  14. Custom Settings
  15. Glossary

Data Conversion Process

Data Conversion Process

You can convert beans from external data sources to Salesforce objects.
Run the data conversion batch job on the external beans and the beans that belong to Salesforce objects. The data conversion job performs the following tasks:
  1. Compares between the following beans and identifies duplicate beans:
    • The external beans that you want to convert with the beans that belong to the Salesforce objects.
    • All the external beans that you want to convert.
  2. Converts all the beans that do not have any duplicates to accounts, contacts, or leads.
The duplicate beans identification before conversion ensures that duplicate beans do not exist in the organization.
If you convert a lead to an opportunity,
CC360
creates tasks for that opportunity. If you do not want to create tasks for the opportunities, set the
Create Opportunity Task
internal setting value to false.
The following sample code sets the value of the internal setting to false:
API_SettingsManager.updateInternalSetting('Create Opportunity Task','false');
The data conversion batch job uses the synchronization settings and the matching settings.
The following image shows how the data conversion batch job converts external beans to Salesforce objects:
The image shows how the data conversion batch job converts beans from external sources to Salesforce objects. The data conversion batch job uses the synchronization settings and the matching settings to convert the external beans to accounts, contacts, or leads.
If you have the Require Validation for Converted Leads flag disabled in the
Lead Settings
page, set the
Disable Validation On Converted Lead
internal setting value to true.
The following sample code sets the value of the internal setting to true:
API_SettingsManager.updateInternalSetting('Disable Validation On Converted Lead','true');

0 COMMENTS

We’d like to hear from you!