Articles in this section

2021 NetSuite bundle releases

  • Release notes for NetSuite Bundle v1.19.1.0, October 2021

    • What’s enhanced

    • What’s fixed

  • Release notes for NetSuite Bundle v1.19.0.0 – SuiteScript, August 2021

    • What's enhanced

    • What's fixed

  • Release notes for NetSuite Bundle v1.17.0.0 – SuiteScript, February 2021

    • What's enhanced

    • What's fixed

{{a name=October}}Release notes for NetSuite Bundle v1.19.1.0, October 2021

{{a name=enhanced_Oct}}What’s enhanced

Support for NetSuite OSS Nexus

European Union customers running the One Stop Shop (OSS) tax configuration can take advantage of full integration support:

  • Importing Sales Orders

  • The Contact Roles sublist is available for the Customer record

Previously, body level imports would reset the line-level fields, generating errors for flows with the OSS setup.

{{a name=fixed_Oct}}What’s fixed

Additional fixes, including for customer-reported issues:

  • NetSuite Contacts and Contact Roles customer sublists were not available for exports or import field mapping

  • In NetSuite custom forms with radio buttons, discount types were not populating flat and percentage values correctly

  • Syncing gift certificates from NetSuite to Salesforce Commerce Cloud would update the wrong item, due to a nlapiSubmitField function limitation for inbound shipment on custom fields

{{a name=August}}Release notes for NetSuite Bundle v1.19.0.0 – SuiteScript, August 2021

{{a name=enhanced_Aug}}What’s enhanced

SuiteScript hooks include required fields for integrator․io hooks

The SuiteScript hook options for preSend, preSavePage, preMap, postMap, and postSubmit now include values for the exportId and importId.

{{a name=fixed_Aug}}What’s fixed

Flow creation and runtime errors for NetSuite v2 accounts

Customers who will be upgraded to NetSuite 2021.2 and use the Celigo NetSuite bundle to integrate with NetSuite v2, such as in Salesforce – NetSuite Integration App v2, would experience the following issues, which are fixed in this release:

  • Unable to save configuration settings on the Edit export panel, with the error “Missing required flow configuration.”

  • Flows were not queuing properly when multiple flows were triggered simultaneously. All flows after the initial flow received error messages to contact Celigo support.

* This fix will be automatically deployed on your NetSuite Production account before you are upgraded to 2021.2; however, you must manually upgrade your Sandbox accounts.

Additional fixes, including for customer-reported issues:

  • integrator․io was not unchecking the Skip export field ID checkbox upon import for records during real-time exports

  • Subrecords for Bin Putaway Worksheet record types were not displayed

  • Salesforce account flows were updating addresses on update actions even when the flow was configured to modify addresses only on creation

{{a name=February}}Release notes for NetSuite Bundle v1.17.0.0 – SuiteScript, February 2021

Important

Important: You must reauthorize your NetSuite connection to work with HMAC 256 authentication.
  • If you have NetSuite 2021.1 installed: Contact support to install NetSuite bundle 1.17 or later and then reauthorize your NetSuite connection.

  • If you have NetSuite 2021.2 installed: Reauthorize your NetSuite connection directly.

NetSuite 2021.2 will be released in June 2021.

{{a name=enhanced_Feb}}What’s new

Suppress errors when deleting items not matching internal ID

The NetSuite import Delete operation excludes fields or files that do not match the search criteria if Ignore missing records is checked.

{{img class=screenshot-frame id=1}}

23962433593371-ns-delete-2.png

{{a name=fixed_Feb}}What’s fixed

Line items in custom fields now support extended characters

Non-alphanumeric characters in data fields, such as < or >, were causing imports to return errors.

Address subrecord fields are now processed immediately after their corresponding body fields

Previously all body fields were sent before their address subrecord fields, causing data to be lost if the fields did not exist.

Partially received inbound shipment records now process correctly

Previously, partially received line items were processed as fully received if the receiveitem field was not set to false.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.