Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Customer 360 for Salesforce Winter 2020
  • All Products

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

Administrator Guide

Administrator Guide

Back Next

Matching Settings for a Record Type

Matching Settings for a Record Type

If the record type is enabled in Salesforce, you can define matching settings specific to each record type of an object class, such as account or contact .
When you run a duplicate check, duplicate contact check, or matching batch job, the batch job looks for matching settings based on the following
CC360
 settings:
  • Use Default Settings
  • Match Using Record Type Rules
The following table lists the matching settings that a duplicate check, duplicate contact check, data conversion, or matching batch job can use based on the
CC360
 Settings:
Match Using Record Type Rules
Use Default Settings
Batch Job Behavior
Enabled
Enabled
The batch job uses the default
CC360
 matching settings.
Enabled
Disabled
The batch job looks for matching settings in the following order:
  1. Matching settings specific to each record type.
  2. If the matching settings are not available for a record type, the batch job looks for the matching settings defined for the object class to which the record type belongs.
    For example, if you do not define matching settings for an account record type named Account:Personal, the batch job looks for the matching settings defined for the Account object class.
  3. If the matching settings are not available for the object class to which the record type belongs, the batch job performs one of the following tasks:
    • If you do not have matching settings for any record type, the batch job uses the default
      CC360
       matching settings.
    • If you have matching settings for at least one record type, the batch job ignores the records.
Disabled
Enabled
The batch job uses the default
CC360
 matching settings.
Disabled
Disabled
The batch job looks for matching settings in the following order:
  1. Matching settings defined for the object class to which the record type belongs.
    For example, for an account record type named Account:Personal, the batch job looks for the matching settings defined for the Account object class.
  2. If the matching settings are not available for the object class to which the record type belongs, the batch job uses the default
    CC360
     matching settings.
0 COMMENTS
We’d like to hear from you!