Chargebee ID and Salesforce ID are case sensitive, while the rest are not. Previously synced records are not affected.Ĭase-sensitivity for comparisons: Whenever field values are compared between Chargebee and Salesforce to find matching records, the comparison is performed in a case-sensitive or case-insensitive manner depending on the property set for the field in Salesforce. The new set of configurations are applied in the next sync after the change. On connecting multiple sites: If you are connecting multiple Chargebee sites to the same Salesforce organization, the considerations discussed in this page is applicable to all the sites.Ĭhanges aren't applied retrospectively: Unless otherwise specified, the changes made to the configuration are applicable only for newly synced records. Chargebee's Solution on Google API Change.Google Play Store Sandbox Configuration.Configurations & Historic Data Processing.Objects and fields mapped between Chargebee and NetSuite.Tax handling in Chargebee - NetSuite Integration.Setting up Token-based Authentication in NetSuite.Accounts Receivable Invoice object mapping.Pre-implementation Settings in Sage Intacct.Reconciling Chargebee Invoices with Xero.Objects and Fields Mapped between Chargebee and QuickBooks.Reconciling Chargebee Invoices with QuickBooks.
PSD2 and Strong Customer Authentication.Worldline Online Payments ePayments via Spreedly.Worldline Online Payments (formerly Ingenico) Direct Integration.
0 kommentar(er)
