New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now
Docschargebee docs
HomeBillingPaymentsRevRecGrowthReveal
Support

Product Updates


  • Release Notes

Getting Started


  • Overview
  • Chargebee Billing Data Centers
  • Object Relationship Model
  • Understanding Sites
  • Chargebee Tech Glossary
  • Articles and FAQ

Implementing Chargebee


  • Implementation Guide
  • Go-live Checklist
  • Articles and FAQ

AI in Chargebee


  • Chargebee Agents
  • Chargebee Copilot
  • Chargebee MCP Server (Model Context Protocol)

Developer Resources


  • Developer Resources Overview
  • Articles and FAQ

Product Catalog


  • Product Catalog Overview
  • Coupons
  • Articles and FAQ

Subscriptions


  • Working with Subscriptions
  • Billing
  • Orders
  • Articles and FAQ

Customers


  • Managing Customers
  • Account Hierarchy
  • Email Notifications
  • Branding
  • Configure Multiple Languages
  • Articles and FAQ

Entitlements


  • Entitlements Overview
  • Features Overview
  • Feature Management
  • Managing Product Entitlements
  • Subscription Entitlements
  • Customer Entitlements
  • Grandfathering Entitlements
  • Articles and FAQ

Usage Based Billing


  • Understanding Usages
  • Setting up Usage Based Billing
  • Usage Alerts
  • Metered Billing
  • Articles and FAQ

Chargebee CPQ


  • Chargebee CPQ
  • Chargebee CPQ for Salesforce
  • Chargebee CPQ for HubSpot

Invoices, Credit Notes, and Quotes


  • Invoices
  • Credit Notes
  • Quotes [Legacy]
  • Transactions
  • Articles and FAQ

Taxes


  • Overview
  • Configuring Taxes
  • Country-specific Taxes
  • Articles and FAQ

Hosted Capabilities


  • Overview
  • Hosted Checkout
  • Hosted Self-Serve Portal
  • Hosted Pages Features
  • Additional Hosted Pages
  • Payment Components
  • Pricing Table
  • Managing Payments with Chargebee.js
  • Mobile-Optimized Hosted Pages
  • Articles and FAQ

Site Configuration


  • Users & Roles
  • Custom Fields & Metadata
  • Approvals
  • Mandatory Fields
  • File Attachments & Comments
  • Advanced Filter Options
  • Multicurrency Pricing
  • Multi-decimal Support
  • Configuring Reason Codes
  • Events and Webhooks
  • API Keys
  • Time Zone
  • Time Machine
  • Transfer Configurations
  • Articles and FAQ

Multi Business Entity


  • Multi Business Entity Overview
  • Customer Transfer Overview
  • Articles and FAQ

Mobile Subscriptions


  • Overview
  • Omnichannel Subscriptions
  • Omnichannel One-Time Orders
  • Mobile Subscriptions (Legacy)

Reports and Analytics


  • RevenueStory
  • Home Dashboard
  • Frequently Asked Questions
  • FAQs for Classic Reports Sunset
  • Articles and FAQ

Integrations


  • Sales
  • Customer Support and Success
  • Finance
  • Tax
  • eInvoicing
  • Marketing
  • Stitch
  • Collaboration
  • Contract Management
  • Ecommerce Management
  • Articles and FAQ

Data Privacy & Security


  • Two Factor Authentication
  • SAML Single Sign-On
  • System for Cross-Domain Identity Management (SCIM)
  • EU-GDPR
  • Consent Management
  • Personal Data Management
  • Compliance Certificates
  • HIPAA Guidelines
  • PCI Recommendations and Integration Types
  • Articles and FAQ

Data Operations


  • Bulk Operations
  • Migration
  • Articles and FAQ
  1. Billing
  2. Integrations
  3. Articles and FAQ
  4. Zendesk
  1. Billing
  2. Integrations
  3. Articles and FAQ
  4. Zendesk

Sync errors in Chargebee Salesforce integration due to duplication rules

Problem Statement

This article helps you understand sync errors in chargebee salesforce integration due to duplication rules.

Solution

This article covers

You can make use of this guide when you get sync errors due to duplication rules.

Summary:

Sync errors that happen due to duplication rules in spite of marking the action as Allow instead of Block. Active Salesforce duplicate rules can conflict with Chargebee that inserts records into your Salesforce organization. When Chargebee integration inserts a new record into Salesforce, the Salesforce duplicate rules are run. If a duplicate is found, the record is not inserted into Salesforce. Most of the integrations that work with Salesforce(including Chargebee) which insert records into Salesforce contain their own built-in duplicate matching rules and should be excluded from the Salesforce built-in duplicate matching rules.

Best Practice

The best practice is to allocate a Salesforce license to integration and assign them to a profile specifically set up for the integration user(s). The profile of the user who had connected Chargebee and Salesforce in this case. This profile can then be excluded from firing the duplicate rules.

There are also some integrations(including Chargebee) whose processes(automations) use the user who set the process up as the creator for new records. These should be reviewed as well as they may also cause records not to be inserted into Salesforce. The fix is to make sure the processes are owned by a user that is excluded from the firing of the duplicate rules.

image

Example:

In the example below, the matching rules have been configured to run only when the Current User is not equal to our two Chargebee related profiles. This will exclude them from the duplicate checking process.

image
  1. What are duplicate rules in SF ?

    A duplicate rule defines what happens during the creation/updation of a duplicate record. Salesforce provides standard duplicate rules for business and person accounts, contacts, and leads. This can also be customized by the client.

  2. How to check duplicate rule setup and indicate the same to the merchant? Ask the merchant to navigate to Setup> Quick Find> search duplicate > click on Duplicate rules. Check with the merchant if these are active and if the alert text matches the error received when syncing the customer.

Was this article helpful?