Table of Contents

Search

  1. Preface
  2. Introduction to Informatica 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 Customer 360 for Salesforce
  7. Managing Duplicate Records
  8. Consolidating Records
  9. Converting External Records to Salesforce Records
  10. Managing Hierarchies
  11. Integrating Customer 360 for Salesforce with Multidomain MDM
  12. Managing Multi-Org
  13. Troubleshooting
  14. Appendix A: Custom Settings
  15. Appendix B: Glossary

Life Cycle of Beans and Master Beans

Life Cycle of Beans and Master Beans

You must run batch jobs or use a data loader to import Salesforce records into
Customer 360 for Salesforce
.
Customer 360 for Salesforce
creates a bean when you first synchronize and import a record into
Customer 360 for Salesforce
.
When you import records,
Customer 360 for Salesforce
performs the following tasks:
  1. Creates beans, if you flag objects for synchronization.
    If you do not flag objects for synchronization, the migrate batch job creates beans for those objects.
  2. Normalizes the data for certain fields to ensure that the data adheres to the standard formats.
    Normalized data ensures that the data is consistent among the beans for certain fields to reduce the chance for the duplication of data and to improve the quality of matching results.
    Customer 360 for Salesforce
    standardizes fields, such as country code, legal form, and domain name.
  3. Creates the fuzzy segment and the external ID.
    The fuzzy segment is a key that
    Customer 360 for Salesforce
    uses as a first step to identify matches. The external ID associates a bean with a source record.
  4. Searches for potential duplicates.
    If you decide that the record is a duplicate,
    Customer 360 for Salesforce
    does not create a bean and the process ends. If
    Customer 360 for Salesforce
    does not identify any potential duplicates or the user indicates that the potential duplicates are not duplicates,
    Customer 360 for Salesforce
    creates the bean.
  5. Sends the normalized data from the bean back to the
    Customer 360 for Salesforce
    Salesforce record.
  6. Creates a master bean.
    For an account bean,
    Customer 360 for Salesforce
    makes a clone of the account bean to create the master bean and adds the bean to the related list of the master bean to link the bean to the master bean. For a contact or a lead bean, the matching batch job matches the bean to a master bean.
    Customer 360 for Salesforce
    adds the bean to the related list of the master bean to link the bean to the master bean and the associated account bean.

0 COMMENTS

We’d like to hear from you!