Knowledge Center

Knowledge Center > Integrations and Extensions > NetSuite Connector > 2016 NetSuite Connector Release Notes > 2015 Z-Suite Integration Release Notes

2015 Z-Suite Integration Release Notes

These Release Notes include enhancements and resolved issues for Z-Suite Integration 2015 Releases.

December 2015 Release, v517

Release Release Date Version
Production December 16, 2015 v517
Sandbox December 10, 2015 v517

Enhancements

Apply List Error for Invoices

The Z-Suite connector now handles apply list errors for Payments when the associated Invoice on the NetSuite side has an amount of $0.

When the connector now detects that an apply list error has occurred, it will update the Payment with the following values:

  • Transferred to Accounting = "Ignore"
  • Integration Status = "Error Applying Payment"

Customers will then be able to perform a manual audit to determine what caused the Invoices to become out of sync between Zuora and NetSuite.

Resolved Issues

The following issue was resolved for this release:

Date-time Comparisons Improvements

Added additional Date-time formats for comparison when the connector is configured to sync New and Updated records to NetSuite for the following use cases:

  • Inconsistent legacy data stored in the sync that did not match current comparison formats.
  • Date value instead of Date-time being passed into the sync.

November 2015 Release, v498

Release Release Date Version
Production November 19, 2015 v501
Sandbox November 12, 2015 v498

 

This release contains a new endpoint update for the Zuora connection. As part of the update process all Z-Suite widgets will be updated to the following endpoints in order to support Payment Method Snapshot object enhancement:

  • Sandbox: https://apisandbox.zuora.com/apps/services/a/60.0
  • Production: https://www.zuora.com/apps/services/a/60.0

The end points are now using a fully qualified URL that defines a specific Zuora WSDL version. The Z-Suite connector now requires at least WSDL v60 and currently supports up to WSDL v68.

Enhancements

Payment Method Snapshot Support

The Z-Suite connector now supports the Payment Method Snapshot object when performing payment syncs. This will allow support for use cases where the Payment Method must be deleted after processing payments.

To enable Z-Suite to reference the Payment Method Snapshot object, navigate to the Advanced Settings of the configuration and set "Use Payment Method Snapshot" to "Yes."

Subscription Number Mapping Improved for Invoice Item Adjustments

The Z-Suite connector now maps Subscription Number at the line level for Invoice Item Adjustments that result in either a NetSuite Invoice or Credit Memo. This change is meant to enable subscription specific NetSuite customizations for adjustments by matching the mapping behavior for Zuora Invoices and Negative Invoices.

Resolved Issues

The following issue was resolved for this release:

Validation Error Occurred on Account Sync When NetSuite Tenant is not Enabled for Multi-currency

When performing a NetSuite Customer-to-Zuora account sync, the currency validation checked the currency of each customer. The validation failed when multi-currency is disabled on the tenant.

Z-Suite now uses the Zuora Default Currency when the NetSuite customer's currency is returned null. NetSuite tenants without multiple currencies to run a NetSuite customer to Zuora account sync without enabling multi-currency.

September 2015 Release, v482

Release Date Version
September 24, 2015 v482

Resolved Issues

The following issue was resolved for this release:

Duplicate Credit Memos Created in NetSuite

Invoice Item Adjustments enter into state that caused duplicate Credit Memos to be created in NetSuite each time the sync ran. Invoice Item Adjustments could not exit this state.

We now check whether Invoice Item Adjustments are in this state before syncing to NetSuite. If an Invoice Item Adjustment is in this state, the following fields are set:

  • Transferred to Accounting = Yes
  • Integration Status = Error Applying Credit Memo

August 2015 Release, v467

Release Release Date Version
Production August 19, 2015  v467

Enhancements

Full Support of Complex Invoice Item Adjustments

In the July release, the following use case was only partially supported when syncing Invoice Item Adjustments:

  • Multiple Subscription, Multiple Rate Plans Per Subscription

This release adds full support for this use case. For more information, see Enhanced Sync of Complex Invoice Item Adjustments in the previous month's release notes.

Resolved Issues

The following issue was resolved for this release:

Date-time Comparison Ignoring Offset

The comparison of the current system time of the sync to the returned time of when the record was last update would ignore the offset provided by Zuora. A new tracked time would not be set until at least 7 or 8 hours later (depending on daylight savings time).

The date-time comparison now properly adheres to all offsets. All system date-time values that are in-use are now standardize across the board.

July 2015 Release, v463

Release Date Version
August 5, 2015 v463

Resolved Issues

The following issue was resolved for this release:

Revenue Recognition Deferred Flag Error

An issue was reported that the deferred flag for all invoice items was being set to true. This was caused by an issue with the revenue recognition start date field mapping on the Invoice Item object.

The deferred flag will now only be set if there is no revenue recognition date set on the Invoice Item object.

July 2015 Release, v420

Release Date Version
July 22, 2015 v420

Enhancements

Added Support to Set Subscription-specific Revenue Recognition Codes for Charges

Prior to this release, changing a Revenue Recognition Code in the Product Catalog affected the NetSuite Revenue Recognition Template for all subscriptions containing an altered charge. This behavior did not align with Zuora behavior for other subscription data.

In this release, Z-Suite now aligns with Zuora behavior with a new option, Yes (Subscription). This new option lets you do the following:

  • Specify a Revenue Recognition Code when creating a subscription.
  • Use the update() call on the RatePlanCharge object. This allows utilizing more Rev Rec Templates in NetSuite for subscription-specific, custom revenue recognition methods.

Choosing the Yes (Subscription) option references the RatePlanCharge.RevRecCode instead of ProductRatePlanCharge.RevRecCode because a subscription-specific Revenue Recognition Code can be set when the subscription is created.

You can navigate to this new option from: Z-Suite Preferences  > Sync Settings > General Revenue and Tax Settings > NetSuite Revenue Recognition.

Enhanced Sync of Complex Invoice Item Adjustments

It was reported that some complex adjustments were resulting in open transactions in NetSuite. For instance, when a subscription is upgraded mid-term and an invoice is generated, it will often contain a combination of charges and credits.

When adjusting Invoices with both charges and credits, we now support fully applying NetSuite Credit Memos created for the resulting Invoice Item Adjustments (IIA) of Type Credit to the Invoices created for the IIAs of Type Charge. The following additional Amend and Invoice scenarios are now supported:

  • One Subscription, One Rate Plan on the Adjusted Invoice
  • One Subscription, Multiple Rate Plans on the Adjusted Invoice
  • Multiple Subscriptions, One Rate Plan per Subscription

Following use case is only partially supported with this release:

  • Multiple Subscription, Multiple Rate Plans Per Subscription

Resolved Issues

The following issue was resolved for this release:

Syncing Invoice Item Adjustment of Type Charge Results in Error

The Zuora Invoice Item Adjustment sync was updated to specify the correct Namespace for the 2014.1 Endpoint where it was found to be hardcoded as an earlier version.

The following error message will no longer occur when syncing Invoice Item Adjustments of Type Charge:

NetSuite Warning: Warning received from NetSuite for record "IIA-00000123":
Error executing Netsuite operation: org.xml.sax.SAXException:
Invalid type: {urn:customers_2010_1.transactions.webservices.netsuite.com}

April 2015 Release, v329

Release Date Version
April 22, 2015 v329

Resolved Issue

Unexpected Error for Zuora Refunds to NetSuite Sync when Syncing Multiple Refunds

The Zuora Refund to NetSuite sync was updated to specify the "replaceAll" flag as "false" explicitly when needed due to a change in behavior between the NetSuite Web Service Endpoints 2010.1 and 2014.1.

The following error message will no longer occur when syncing multiple refunds per customer at the same time:

NetSuite Warning: Warning received from NetSuite for record "R-00003681": (Error Received during Netsuite Update
Code: USER_ERROR
Type: ERROR
Message: All lines of sublist applyList have to be specified when replace All is requested.

March 2015 Release, v328

Release Date Version
March 11, 2015 v328

Important

This release contains a new endpoint update. As part of the update process all Z-Suite widgets will be updated to use the new endpoint. Users are required to re-enter their username and password for NetSuite and Zuora credentials. See Required Action for Z-Suite March 2015 Release.

Enhancements

Added Beta Prerelease to NetSuite Environment list in Connection Information

We have included the NetSuite Beta Prerelease API Endpoint Environment to support testing of Z-Suite prior to the release of updates to NetSuite as desired.

See Configure Connection Information.

Resolved Issues

The following issues were resolved for this release:

Unsupported Country Value results in Validation Warning

The API Endpoint for NetSuite has been updated to be using version 2014.1 which enabled support for the following countries to Z-Suite:

  • Aland Islands
  • Curaçao
  • Bonaire, Saint Eustatius and Saba
  • Cape Verde
  • Falkland Islands (Malvinas)
  • Saint Barthelemy
  • Saint Helena
  • Saint Martin (French part)
  • Sint Maarten
  • Samoa

The following message will no longer occur for Contacts with the above country in their address:

Validation Warnings:

Customer Account "123456" had the following validation warnings and was not synced:
Unsupported Country Value for Bill to Country [*Country Name Here*]. Please choose a supported country and try again.
Unsupported Country Value for Sold to Country [*Country Name Here*]. Please choose a supported country and try again.

 

January 2015 Release, v321

Release Date Version
January 28, 2015 v321

Enhancements

Error Handling: New NetSuite Error Limit for Debugging Preference

A new preference for Debug Logging has been added to Z-Suite Advanced Sync Preferences to allow for 50 to 5,000 errors to be recorded in process logs per sync when debug logging is enabled. This allows for the logging of errors beyond a 10,000 character limit that previously prevented this. For performance, the 10,000 character limit for NetSuite errors is still in place when debugging is not enabled.

See Configure Advanced Settings for more information.

Resolved Issues

The following issues was resolved for this release.

Parent/Child Z Customer Accounts to NetSuite Sync Error

Addressed issue that would prevent successfully associating a Child account with it's Parent account in NetSuite after the initial creation of both accounts. This error should no longer appear in Process Logs for the above scenario:

First document failure: [Function: Get RECORD_DETAILS Property, Scripting (Step 2)]: Error executing custom script: Process Property 'RECORD_DETAILS' has not been initialized. (in groovy script); Caused by: Process Property 'RECORD_DETAILS' has not been initialized. (in groovy script); Caused by: Process Property 'RECORD_DETAILS' has not been initialized.

Unsupported Country values for Contacts results in Unexpected Error

Previously, when an unsupported country was encountered for a contact record, the process logs would record a nonspecific unexpected error and halt further processing of records.

Now, error handling has been changed to allow for the recording of a more useful message advising that the Country does not match a value available in NetSuite and therefore is not supported and must be changed. For example:

 

Validation Warnings: Customer Account "A00000123" had the following validation warnings and was not synced:
No Bill to Country cross reference match found for value ["YourUnsupportedCountryShowsHere"]. Please correct any discrepancies between Zuora and NetSuite and try again.

Last modified
12:07, 19 Jan 2016

Tags

Classifications

(not set)