InCountry logo
mobile-nav
Search
  • Products
    • Products
      • InCountry for Salesforce
      • Data Residency-as-a-Service
      • Alibaba Cloud InCountry Service
      • Compliance and security
    • Gateways
      • Email
      • Payment Vault
      • Web Forms
      • HTML
    • Developers
      • REST API
      • SDK
  • Solutions
    • Automotive
    • Energy
    • Financial services
    • Healthcare
    • Retail
    • Technology
    • Latest success story
      • IBM Consulting
  • Integrations
    • Cegid
    • Intertrust
    • MuleSoft
    • PayPal
    • Salesforce
    • ServiceNow
    • Stripe
    • Veeva Systems
    • Yandex
  • Resources
    • Country compliance
    • Documentation
    • Library
    • Partners
    • Pricing
  • About
    • News and Blog
    • Careers
    • Contact Us
    • FAQ
    • Leadership
  • Login
  • Schedule a Demo

›User's guide

Home
  • InCountry Platform
Portal
  • Getting started
  • Documentation
    • Dashboard
    • Managing environments
    • Managing SDK credentials and services
    • Managing Border configuration
    • Managing payment vaults
    • Managing email gateways
    • Managing resident functions
    • Managing file imports
    • Managing profile and organization
    • Managing users
    • Managing encryption keys
  • Release notes
Border
  • Documentation
  • Release notes
REST API
  • Documentation
  • How to test CRUD requests through REST API
  • Release notes
Resident Functions
  • Documentation
Salesforce
  • About
  • Overview
  • Quick start guide for three-model package
  • Quick start guide for legacy package
  • Administrator's guide
    • Managing the package
    • Managing permissions
    • Managing OAuth2 authentication and authorization
    • Managing certificates
    • Registering CSP Trusted Sites
    • Managing InCountry Endpoints
    • Managing REST endpoints
    • Managing InCountry flags
    • Loading the application
    • Managing data regulation policies
    • Managing protected fields
    • Hashing the UserName field
    • Managing custom objects
    • Replacing standard elements
    • Configuring record search
    • Managing components
    • Setting up Salesforce Experience Cloud
    • Managing resident functions
    • Managing InCountry cache
    • Managing Apex triggers
    • Managing record synchronization
    • Managing web forms
    • Tracking changes to data regulation policies and regulated fields
    • Using Email-to-Case feature
    • Debugging
    • Migrating data from one Salesforce organization to another
  • Developer’s guide
    • Apex SDK
    • JavaScript API
    • Retrieving record statistics
    • Tracking field history
  • User's guide
    • Working with protected fields
    • Sending compliant email messages
    • Importing data into Salesforce
    • Migrating records
    • Managing audit reports
    • Converting leads
    • Managing reports
    • Using formula fields
    • Using frontend validations
    • FAQ
    • Release notes
Payment Vault
  • Documentation
BYOK
  • Documentation
FAQ
  • Get started with the platform
  • Integration options
  • Data regulation models
  • Limits and quotas
  • Video tutorials
Service Status
  • Status

Converting leads

note

Conversion of leads is supported in the legacy package and in the three-model package for the redaction and restrictions models.

The Lead Convert component converts a lead into an account and contact, as well as an opportunity.

To convert a lead:

  1. On the Leads tab, open the lead record.

  2. At the top right part of the page, click Convert.

    Convert

  3. In the Convert Lead form, define the type of record you want to convert the current lead into.

    Define the type of record

  4. In the Account section, select Create New and enter the account name if you want to convert your lead into an account, or select Choose Existing and pick the appropriate account for lead conversion.

  5. In the Contact section, select Create New and enter the contact name if you want to convert your lead into a contact, or select Choose Existing and pick the appropriate contact for lead conversion.

  6. In the Opportunity section, select Create New and enter the opportunity name if you want to convert your lead into an opportunity, or select Choose Existing and pick the appropriate opportunity for lead conversion. You can also choose the Don’t create an opportunity upon conversion option if you don't want to create an opportunity.

  7. Verify the record owner and converted status in the corresponding fields.

  8. Click Convert.

note

Please take into account the following points:

  1. A lead can be converted to regulated and non-regulated objects.

  2. The lead must always be a regulated object.

  3. To convert a lead to other objects in other countries, you must have access to this country. (For example,

    1. A user OUTSIDE OF the country treated under the redacted policy cannot convert a record to the lead pertaining to the country managed under the redacted policy.

    2. A user FROM the country treated under the redacted policy can convert a lead to the record that can be attributed to the country treated under the redacted policy and to the record that can be treated under the restricted or replicated policy.

  4. To convert a lead record according to the applied record policy, the lead record pending conversion must have a record-level policy applied.

How to view duplicates on Lead Convert dialogue

The InCountry Data Residency package supports the duplicate detection mechanism allowing users to see potential duplicates during the lead conversion process.

Prerequisites

To view potential duplicates, you need to do the following:

  1. In the App Launcher form, select InCountry.

  2. Select Settings.

  3. Expand the InCountry Flags section.

  4. Enable the Show duplicates on Lead Convert popup flag.

After that, you need to create matching and duplicate rules. For the details on how to configure them, please check Salesforce documentation.

Checking the duplicates

Once you have configured the duplicate and matching rules in Salesforce, you can proceed with conversion of leads to other Salesforce objects. Upon identification of potential duplicates, the Convert Lead form will indicate such duplicated records.

To see duplicates in the Opportunity section, you must select the Account record, then the Lead Convert component makes a request to find all opportunities associated with the selected account:

If you ignore the block action in the duplication rule, then you will see the following error:

Considerations

  • The duplicate record check is performed only when the Lead Convert form is displayed.

  • The duplicate detection mechanism uses the full-text match to identify duplicates. It pulls values of fields used for duplicate matching, hashes them, and checks them against values of the Account, Contact, Opportunity, and Person objects stored in Salesforce database. Upon matching identical hashes, the mechanism pulls duplicated records from Salesforce and shows them to you.

  • If the allow action is used in duplicate rules then you can convert leads without selecting anything, if the block action is used in duplicate rules then you must select one of the existing records.

  • The duplicate detection mechanism can handle up to 50 potential duplicates per object.

  • The search layouts of Salesforce objects are used to display fields of potential duplicates.

  • Hash functions that are applied to similar fields (for example, First Name and Last Name) should be identical across all Salesforce objects against which duplicate rules are checked. If hash functions differ, the duplicate mechanism may not find the proper matches. Additionally, after the lead conversion you may receive an error without a capability to roll back your changes.

  • When Salesforce Lead Fields Map is used for regulated fields, you must copy these rules to InCountry Lead Convert Mapping.

← Managing audit reportsManaging reports →
  • How to view duplicates on Lead Convert dialogue
    • Prerequisites
    • Checking the duplicates
    • Considerations
InCountry logo blue
© InCountry 2022.
All rights reserved. InCountry, Inc
  • PRIVACY POLICY
  • TERMS OF SERVICE
  • Social share
    • YouTube logo
    • Facebook logo
    • Twitter logo
    • LinkedIn
  • Column 1
    • Products
      • Products
        • InCountry for Salesforce
        • Data Residency-as-a-Service
        • Alibaba Cloud InCountry Service
        • Compliance and security
      • Gateways
        • Email
        • Payment Vault
        • Web Forms
        • HTML
      • Developers
        • REST API
        • SDK
  • Column 2
    • Solutions
      • Automotive
      • Energy
      • Financial services
      • Healthcare
      • Retail
      • Technology
    • Integrations
      • Cegid
      • Intertrust
      • MuleSoft
      • PayPal
      • Salesforce
      • ServiceNow
      • Stripe
      • Veeva Systems
      • Yandex
  • Column 3
    • Resources
      • Country compliance
      • Documentation
      • Library
      • Partners
      • Pricing
    • About
      • News and Blog
      • Careers
      • Contact Us
      • FAQ
      • Leadership