Zuora 360+ Release Notes

Resolved: Zuora 360+ incorrectly syncing new invoice owner value to all versions of subscription

Previously, when you performed an owner transfer amendment, you might encounter the issue where Zuora 360+ incorrectly synced the new invoice owner value to all versions of the subscription within the subscriptionHistory object. This issue is now resolved.

We have updated the sync logic for Zuora 360+ so that the correct invoice owner value for each subscription version will synchronize to Salesforce, ensuring the same data in both systems.

Resolved issue: Deleted subscription and child rate plan not synced due to sync unreliability

Previously, subscription and its child rate plan charges in Salesforce were sometimes not removed after the counterparts were deleted in your Zuora tenant because of sync unreliability. We have enhanced the sync reliability so that deleted subscription rate plan charges in Zuora are also removed more reliably in Salesforce. Thus this issue has been resolved.

Resolved issue: UseDefaultRetryRule not synced with PaymentMethod

Previously, you might encounter the issue where the UseDefaultRetryRule field (Zuora__UseDefaultRetryRule__c) failed to sync with PaymentMethod field (Zuora__PaymentMethod__c). This issue has been resolved now.

Resolved: Data not synced caused by daylight saving change

Previously, some data created around the cutover time where Pacific Daylight Time (PDT) switches to Pacific Standard Time (PST) were not picked up by Zuora 360+ for the sync. This issue has been resolved now.

Resolved: Retry UI page taking long time to process requests

Previously, you might encounter the issue where the retry UI page took a long time to process requests and was unresponsive. This issue has been resolved.

Resolved: Objects not synced to Salesforce

Previously, after a tenant was throttled due to SFDC connection failures, objects would not properly sync to SFDC after the connection was restored. This issue has been resolved.

Resolved: Deleted subscription rate plan charges not synced due to sync unreliability

Previously, subscription rate plan charges in Salesforce were sometimes not removed after the counterparts were deleted in your Zuora tenant because of sync unreliability. We have enhanced the sync reliability so that deleted rate plan charges in Zuora are also removed more reliably in Salesforce. Thus this issue has been resolved.

Resolved: Rate Plan Charge History object not resynced after dependent object is synced

By design, the Rate Plan Charge History object can be synced only after the dependent object is synced. Previously, if the Rate Plan Charge History object could not be synced for this reason for the first time, Zuora 360+ could not retry the Rate Plan Charge History object sync after the dependent object was synced. 

This issue is now resolved. We have updated the resync logic of Zuora 360+ so that the Rate Plan Charge History object sync is retried once the dependent object is synced.

Resolved: Account object cannot resync when the Contact object is updated

Previously, you might encounter the issue where the Account object failed to resync if a contact object was updated. This issue has been resolved now.

Zuora 360+ now supports syncing Opportunity fields

Zuora 360+ now supports syncing Opportunity fields to Salesforce in real-time. We have also protected this feature behind the SUBSCRIPTION_QT feature in the transformer.

Resolved: Zuora 360+ not syncing Product custom fields to Salesforce

Previously, you might encounter the issue where Zuora 360+ was not syncing Product custom fields to Salesforce. This issue is now resolved.

Resolved: Product sync adds "Billing Period" as a new picklist to ListPriceBase value

Previously, Zuora 360+ Product sync adds the Billing Period value as a new picklist to ListPriceBase value on Product Rate Plan Charge. We have now updated the picklist terms to align with Salesforce.

We have made the following changes: 

• Billing Period to Per Billing Period
• Month to Per Month
• Week to Per Week

Resolved: Currency custom fields not synced to Salesforce 

Previously, you might encounter the issue where the custom fields of the Currency type were not synced into your Salesforce org. We have resolved this issue. The Currency type custom fields in Zuora are now synced to Salesforce correctly.

Resolved: Deleted subscription rate plan charges not synced due to sync unreliability

Previously, subscription rate plan charges in Salesforce were sometimes not removed after the counterparts were deleted in your Zuora tenant because of sync unreliability. We have enhanced the sync reliability so that deleted rate plan charges in Zuora are also removed more reliably in Salesforce. Thus this issue has been resolved.

Resolved: Rate Plan Charge History object not resynced after dependent object is synced

By design, the Rate Plan Charge History object can be synced only after the dependent object is synced. Previously, if the Rate Plan Charge History object could not be synced for this reason for the first time, Zuora 360+ could not retry the Rate Plan Charge History object sync after the dependent object is synced. 

This issue is now resolved. We have updated the resync logic of Zuora 360+ so that the Rate Plan Charge History object sync is retried once the dependent object is synced.

Resolved: Suscription Product Charge History fields not synced to salesforce

Previoulsy, the following fields of the Subscription Product Charge History object in Zuora were not synced to the Zuora_SubscriptionProductChargeHistory__c object in Salesforce through Zuora 360+:

• Quantity
• Model
• Period

We have resolved this issue and these fields are now correctly synced.

Resolved: Custom Date field not synced if value is null

Previously, you were likely to encounter the issue where each of the custom fields of the Date type were not synced to Salesforce through Zuora 360+ when the value is set to null. This issue is now resolved.

Resolved: Invoice items not synced caused by daylight saving change

Previously, some invoice items created around the cutover time where Pacific Daylight Time (PDT) switches to Pacific Standard Time (PST) were not picked up by Zuora 360+ for the sync. This issue has been resolved now.

Resolved: Deleted subscriptions in Zuora not synced to Salesforce

Previously, if you used jobs that run in Salesforce to delete subscriptions from Zuora on a regular basis, you might encounter the issue where some deleted subscriptions were not synced to Salesforce successfully through Zuora 360+. This issue is now resolved.

Resolved: Invoice items not synced because of row locking error

Previously, you might find that multiple invoice items updates were not synced successfully through Zuora 360+ because of the following error:

UNABLE_TO_LOCK_ROW: unable to obtain exclusive access

We have enhanced the internal retry logic and this issue has been resolved now.

Resolved: Invoice sync failed with Internal error

Previously, you might encounter the issue where the ​​Invoice object sync with Zuora 360+ failed with internal error. This issue has been resolved now.

Zuora 360+ now supports syncing Product Catalog objects 

Zuora 360+ now supports syncing Product Catalog objects to Salesforce in real time. The fields on the following objects can be synced through Zuora 360+:

• Product
• Product Features
• Product Rate Plan
• Product Rate Plan Charge
• Product Rate Plan Charge Tier

To sync Product Catalog objects through Zuora 360+, you must ensure that Zuora Quotes has been set up, and Product Catalog is enabled in the 360+ Object Enablement setting.

For more information, see the following articles:

• Sync Field Mapping of Product Catalog and Related Objects for Zuora 360+
• Manage Objects and Sync Results for Zuora 360+

Improved package querying performance

Zuora 360+ is built on top of the Zuora 360 package. For better user experience during the installation of the Zuora 360 package, we have now improved the performance of package querying on the back-end.

Throttling on invalid credentials

To improve performance, throttling has been introduced to limit the number of times users can enter expired or invalid Salesforce passwords.

Resolved: Currency mapping discrepancy

Previously, there was currency mapping discrepancy between Zuora and Salesforce. For example, the New Romanian Leu was used in Zuora 360+ but New Leu was used in Zuora Billing, which caused errors. It was because the currency library used by Zuora Billing was different from the one used by Zuora 360+. This issue has been resolved now.

Resolved: Customer account sync failure after updating Tax Exempt Expiration Date 

Previously, if you created a customer account in Zuora, then update the standard Tax Exempt Expiration Date field with a specific date, the sync of this account would fail due to an invalid field type error. This issue has been resolved now.

Resolved: Sync issues for Subscription Rate Plans and Subscription Rate Plan Charges

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

Resolved: Zuora 360+ failed to delete charges that have been removed from subscription

Previously, you might find that Zuora 360+ did not delete subscription product charges that have been removed from the subscription in some cases. This issue has been resolved now.

Resolved: Missing charge number in Zuora 360+ records

Previously, if rate plan charges did not get synced from Zuora to Salesforce with its corresponding charge number and you tried to resync, a duplicate record would be created. This issue has been resolved now. Rate plan charge records that miss the charge numbers will be dropped.

Resolved: Error message not clear when CRM ID is missing

Previously, if CRM ID was not available on the account during the sync of a subset of record types such as Credit Memo Part, Refund Part, and Payment Part, an error would occur but the error message was not user-friendly. We have now improved the error message to ensure it clearly describes the issue.

Resolved: 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: 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: 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.

Resolved: 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.

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: 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: 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: 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.

Resolved: 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.

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: 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.

Resolved: 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: 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: 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+.

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: 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: 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.