Zuora Data Sync for Salesforce CRM Release Notes
We publish Zuora Data Sync for Salesforce CRM Release Notes when customer-facing features, enhancements, and resolved issues of Zuora Data Sync for Salesforce CRM are deployed to Zuora Sandbox environments.
These release notes provide a summary of new features, enhancements, and resolved issues in the Zuora Data Sync for Salesforce CRM.
March 28, 2023
Support for syncing Draft Billing Accounts
Previously, syncing of Draft Billing Accounts was not supported. However, this feature has been added in the new version, and now you can sync your Draft Billing Accounts. This will enable you to have greater control and flexibility over your billing accounts, allowing you to make changes and updates to your billing information.
Resolved: Subscription rate plan charges not synced due to sync unreliability
Previously, you might have encountered an issue where data connect sometimes deleted Subscriptions and Rate Plan Charges because of sync unreliability. Thus this issue has been resolved.
March 15, 2023 (Maintenance Release 5.16)
Support for new field in ZContact object
In Zuora Data Sync for Salesforce CRM, we have added a new field called Zuora__CustomerAccount__c to Zuora__ZContact__c. In Salesforce 5.16, this field corresponds to the CustomerAccount object.
February 10, 2023
Support for encrypting Objects and Fields in Salesforce
In Zuora Data Sync for Salesforce CRM, objects and fields in Salesforce can now be encrypted using Salesforce Shield.
Resolved issue: Zuora Data Sync does not retrigger child objects when the parent object has been synced with 360
Previously, you might have encountered an issue where Zuora Data Sync did not retrigger the child objects after the parent object was synced with 360. This issue has been resolved.
Resolved issue: Rate Plan History and Rate Plan Charge History objects not synced to Salesforce
Previously, the Rate Plan History and Rate Plan Charge History records were not synced in Salesforce. This is because if both the object and the history version of the object have the same id, retrying by id does not necessarily retry both entries. This issue has been resolved.
Resolved issue: Custom fields not synced properly
Previously, you might have encountered an issue resulting in some records not being synced properly when deleting custom fields. This issue has been resolved.