Skip to main content

Zuora 360+ Release Notes

Zuora

Zuora 360+ Release Notes

We publish Zuora 360+ Release Notes when customer-facing features, enhancements, and resolved issues of Zuora 360+ are deployed to Zuora Sandbox environments.

For the release notes of Zuora 360, see Zuora 360 Version 5 Release Notes.

June 14, 2021

Resolved issue: Subscription sync failure when amendments were created

Previously, when amendments were created, you might find that the sync of Subscription records failed due to a duplicate external ID error. This issue occurred because multiple versions of the same subscription were picked up by Zuora 360+ as active versions, despite the fact that only the latest version is active. We have enhanced the version checking mechanism, and this issue has been resolved.

Resolved issue: Rate Plan Charge with latest segment not synced

Previously, for rate plan charges that have multiple segments, the charge with the latest segment was not synced through Zuora 360+. This issue occurred because the version check was not performed. We have enhanced the version checking mechanism, and this issue has been resolved.

Resolved issue: Taxation Item Id in Zuora synced to Taxation Item Name in Salesforce

After you have enabled the Taxation Item object for Zuora 360+, the Taxation Item Id in Zuora was previously incorrectly synced to the Taxation Item Name field in Salesforce. This issue has been resolved now. The Taxation Item Id and Taxation Item Name fields from Zuora are now synced to Taxation Item Id and Taxation Item Name in Salesforce, respectively.

June 3, 2021

Resolved issue: Rate Plan History and Rate Plan Charge History not synced

In extreme cases, Rate Plan History and Rate Plan Charge History records were not synced in Zuora 360+. This issue has been resolved.

May 19, 2021

Zuora Salesforce package verification

With Zuora 360+ enabled, whether the installed Zuora Salesforce package version supports syncing the configured objects will be verified. Previously, no verification was performed.

Note that this enhancement requires that the profiles of sync users must have the View All Custom Settings system setting enabled in the Salesforce organization. It is to ensure sync users can read the Zuora Config custom setting. If they cannot read this setting, object syncs will be throttled.

Automated child objects resynchronization

With Zuora 360+ enabled, when a parent object fails to start syncing, its child objects will be logged and retried.

Resolved issue: Sync failure for invoices, invoice items, and payments 

Previously, you might find that invoices, invoice items, and payments were not successfully synced when Zuora 360+ tried to sync a large number of invoices, invoice items, and payments at the same time. This issue has been resolved now.

Resolved issue: Sync failure for email or currency type custom fields

Previously, Zuora 360+ would fail to sync custom fields if the custom fields were of the email or currency type. This issue has been resolved.

Resolved issue: Subscription charge not deleted after removing products

In extreme cases, after you remove products in an order, the charge of the subscription was not deleted by Zuora 360+. This issue has been resolved now.

April 29, 2021

Resolved issue: Subscription History records incorrectly synced

In extreme cases, Subscription History records such as Subscription Name, version, and Subscription Start Date were not synced or incorrectly synced. This issue has been resolved now.

March 18, 2021

Support for Balance field on Invoice Item object

With Zuora 360+ enabled, the Balance field is now available on the Invoice Item object in Salesforce (Zuora__Invoice__Balance__Amount__c). It allows you to view invoice item balance within Salesforce.

To take advantage of this enhancement, you must ensure that you are on Zuora 360 version 5.10 or a later version.

See New object types supported only when Zuora 360+ enabled for more information.

Resolved issue: Cannot sync Account object when account currency is JPY

Previously, you might fail to sync the Account object via Zuora 360+ if the currency of the account was JPY. This issue has been resolved now.

March 3, 2021

Resolved issue: Zuora payment ID used for Payment Method Name with Zuora 360+ enabled

Previously, with Zuora 360+ enabled, Zuora used Zuora payment ID for the Payment Method Name field on the Payment Method object in Salesforce. To be consistent with Zuora 360, Salesforce payment method record ID is now used for the Payment Method Name field.

Resolved issue: DACO-99 error on SubscriptionRatePlan and SubscriptionRatePlanCharge objects

Previously, you might encounter the DACO-99 error code that prevented the synchronization of Subscription Rate Plans and Subscription Rate Plan Charges when performing syncs. This issue has been resolved now.

Resolved issue: Credential synchronization issue

Previously, updates to Salesforce credentials were not retrieved and activated to support Zuora 360+. This issue has been resolved now.

Note that after you update the Salesforce credential, it might take up to 10 minutes for the update to take effect in Zuora 360+.

January 21, 2021

New text field added to SubscriptionProductChargeHistory object 

The Product Rate Plan Charge Id (Zuora__ProductRatePlanChargeId__c) text field has been added to the Subscription Product & Charge History (Zuora__SubscriptionProductChargeHistory__c) object in Zuora 360+. To take advantage of this enhancement, you must ensure that you are on Zuora 360 version 5.8 or a later version.

See New object types supported only when Zuora 360+ enabled for more information.

Resolved issue: Type field not synced on SubscriptionProductChargeHistory

Previously, The values for the Type (Zuora__Type__c) field on the Subscription Product & Charge History (Zuora__SubscriptionProductChargeHistory__c) object were not synced from Zuora. This issue has been resolved now.

Resolved issue: Subscription custom fields not synced with Zuora 360+ enabled

Previously, with Zuora 360+ enabled, custom fields on the Subscription object were likely to be ignored and could not get synced into Salesforce. This issue has been resolved now.