---
schema_version: "1"
id: ee92013edd88b8c79f6bb2aded4040aeec4c0736e68dbab0cb0357cfad3f91c5
title: Upgrading and Migrating to NetSuite Connector 11.x
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/netsuite-connector/11.11/netsuite-connector-upgrade-migrate.md
canonical_url: https://docs.mulesoft.com/netsuite-connector/11.11/netsuite-connector-upgrade-migrate
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 95cfc280f75e8ab2958875946a31b58c681eb13dc7e8ac129d03fc3d1d779e49
description: MuleSoft Documentation Site
release: "11.11"
latest: false
---
---
product: NetSuite Connector
version: 11.11
---

# Upgrading and Migrating to NetSuite Connector 11.x

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Upgrade NetSuite Connector to version 11.x to use the new features.

## Supported Upgrade Paths

<table><colgroup><col> <col></colgroup><thead><tr><th>From Version</th><th>To Version</th></tr></thead><tbody><tr><td><div><div><p>10.x</p></div></div></td><td><div><div><p>11.x</p></div></div></td></tr></tbody></table>

## Changes in This Release

In NetSuite Connector 10.x, the connector resolved metadata by receiving Java objects as input, and
converting those objects internally to XML, so that NetSuite could understand it. In NetSuite
Connector 11.x, XML metadata is resolved directly without the need for conversion.

Because of this modification, the input and output metadata for connector operations has changed and
is now equivalent to the request and response bodies of the corresponding SOAP API operations. You
can use DataSense explorer in Studio to drag and drop the metadata fields, which generates their
corresponding namespaces and tags automatically.

Version 11.x also eliminates the REST-based operations.

## Changes to Sources

Removed the **Page Size** field for the sources **On Deleted Object**, **On Modified Object**, and
**On New Object**. Each source now returns one record in the output metadata.

> [!NOTE] In NetSuite Connector 11.10, the **On Deleted Object** source supports page size.

## Changes to Operations

### Advanced Operations

Changes to advanced operations include the following:

<table><colgroup><col> <col></colgroup><thead><tr><th>Operation</th><th>Changes</th></tr></thead><tbody><tr><td><p>Change Email</p></td><td><p>Returns a NetsuiteSoapAttributes object in the output metadata</p></td></tr><tr><td><p>Change Password</p></td><td><p>Returns a NetsuiteSoapAttributes object in the output metadata</p></td></tr><tr><td><p>Get Account Governance Info</p></td><td><p>Returns a GetAccountGovernanceInfoResult object in the output metadata</p></td></tr><tr><td><p>Get Data Center URLs</p></td><td><p>Returns a NetsuiteSoapAttributes object in the output metadata.</p></td></tr><tr><td><p>Get Integration Governance Info</p></td><td><p>Returns a GetIntegrationGovernanceInfoResult object in the output metadata</p></td></tr><tr><td><p>Get Server Time</p></td><td><p>Returns a NetsuiteSoapAttributes object in the output metadata</p></td></tr></tbody></table>

### Async Operations

Each operation now returns a NetsuiteSoapAttributes object in the output metadata. Other changes to
the async operations include the following:

<table><colgroup><col> <col></colgroup><thead><tr><th>Operation</th><th>Changes</th></tr></thead><tbody><tr><td><p>Async Add List</p></td><td><p>Removed the Record Type and Records fields. You now specify the associated values in the Message field of the input metadata.</p></td></tr><tr><td><p>Async Delete List</p></td><td><p>Removed the Deleted Base Ref Types field. You now specify the associated values in the Message field of the input metadata.</p></td></tr><tr><td><p>Async Delete List Records</p></td><td><p>Removed this operation. For equivalent functionality, use the Async Delete List operation and specify the recordRef or baseRefType in the Message field of the input metadata.</p></td></tr><tr><td><p>Async Get List</p></td><td><p>Removed the Retrieved Base Ref Types field. You now specify the associated values in the Message field of the input metadata.</p></td></tr><tr><td><p>Async Get List Records</p></td><td><p>Removed this operation. For equivalent functionality, use the Get List operation and specify <code>FILE</code> as the record type in the Message field of the input metadata.</p></td></tr><tr><td><p>Async Initialize List</p></td><td><p>Removed the Initialize Records field. You now specify the associated values in the Message field of the input metadata.</p></td></tr><tr><td><p>Async Search</p></td><td><p>Removed the Search Record and Criteria fields. You now specify the associated values in the Message field of the input metadata.</p></td></tr><tr><td><p>Async Update List</p></td><td><p>Renamed Record Type to Type. Removed Records attributes. You now specify the associated values in the Message field of the input metadata.</p></td></tr><tr><td><p>Async Upsert List</p></td><td><p>Renamed Record Type to Type. Removed Records attributes. You now specify the associated values in the Message field of the input metadata.</p></td></tr><tr><td><p>Check Async Status</p></td><td><p>No changes.</p></td></tr><tr><td><p>Get Async Result</p></td><td><p>No changes.</p></td></tr></tbody></table>

### Invitee Operations

Each invitee operation now returns a NetsuiteSoapAttributes object in the output metadata. Other
changes to the invitee operations include the following:

<table><colgroup><col> <col></colgroup><thead><tr><th>Operation</th><th>Changes</th></tr></thead><tbody><tr><td><p>Update Invitee Status</p></td><td><p>Removed the Event ID and Status fields. You now specify these values in the Message field of the input metadata.</p></td></tr><tr><td><p>Update Invitee Status List</p></td><td><p>Removed the Record Type and Invitee Statuses fields. You now specify these values in the Message field of the input metadata.</p></td></tr></tbody></table>

### Item Operations

Each item operation now returns a NetSuiteSoapAttributes object in the XML metadata. Other changes
to the invitee operations include the following:

<table><colgroup><col> <col></colgroup><thead><tr><th>Operation</th><th>Changes</th></tr></thead><tbody><tr><td><p>Get Budget Exchange Rates</p></td><td><p>New operation that returns a list of budget exchange rates for a specified period.</p></td></tr><tr><td><p>Get Customization Id</p></td><td><p>New operation that returns the IDs of available customizations for a given customization type.</p></td></tr><tr><td><p>Get Currency Rate</p></td><td><p>Removed the Rate Filter field. You now specify this value in the Message field of the input metadata.</p></td></tr><tr><td><p>Get Item Availability</p></td><td><p>Removed the Record and If Modified Since fields. You now specify these values in the Message field of the input metadata.</p></td></tr><tr><td><p>Get Posting Transaction Summary</p></td><td><div><div><ul><li><p>Removed the Fields, Filters, and Page Index fields. You now specify these values in the Message field of the input metadata.</p></li><li><p>Returns a postingTransactionSummaryList object in the payload of the output metadata.</p></li></ul></div></div></td></tr></tbody></table>

### Record Operations

Changes to record operations include the following:

<table><colgroup><col> <col></colgroup><thead><tr><th>Operation</th><th>Changes</th></tr></thead><tbody><tr><td><p>Add File</p></td><td><p>Removed this operation. For equivalent functionality, use the Add operation and specify <code>FILE</code> as the record type in the Message field of the input metadata.</p></td></tr><tr><td><p>Add List</p></td><td><div><div><ul><li><p>Removed the Record Maps field. You now specify this value in the Message field of the input metadata.</p></li><li><p>Returns an addListResponse object in the palyload of the output metadata.</p></li></ul></div></div></td></tr><tr><td><p>Add Record</p></td><td><div><div><ul><li><p>Renamed to Add.</p></li><li><p>Removed the Attributes field. You now specify the associated values in the Message field of the input metadata.</p></li><li><p>Returns a NetsuiteSoapAttributes object in the output metadata.</p></li></ul></div></div></td></tr><tr><td><p>Add Record Objects</p></td><td><div><div><p>Removed this operation. For equivalent functionality, use the Add List operation.</p></div></div></td></tr><tr><td><p>Attach Record</p></td><td><div><div><ul><li><p>Renamed to Attach.</p></li><li><p>Removed the Source, Destination, and Contact fields. You now specify the associated values in the Message field of the input metatada.</p></li><li><p>Returns a NetsuiteSoapAttributes object in the output metadata with an attached object as the payload..</p></li></ul></div></div></td></tr><tr><td><p>Delete</p></td><td><div><div><ul><li><p>Removed the Base Ref field. You now specify the associated values in the Message field of the input metatada.</p></li><li><p>Returns a deleteResponse object in the payload of the output metadata.</p></li></ul></div></div></td></tr><tr><td><p>Delete List</p></td><td><div><div><ul><li><p>Removed the Deleted Base Ref Types field. You now specify the associated values in the Message field of the input metatada.</p></li><li><p>Returns a NetsuiteSoapAttributes object in the output metadata.</p></li></ul></div></div></td></tr><tr><td><p>Delete Record</p></td><td><p>Removed this operation. For equivalent functionality, use the Delete operation.</p></td></tr><tr><td><p>Delete Records List</p></td><td><p>Removed this operation. For equivalent functionality, use the Delete List operation.</p></td></tr><tr><td><p>Detach Record</p></td><td><div><div><ul><li><p>Renamed to Detach.</p></li><li><p>Removed the Source and Destination fields. You now specify the associated values in the Message field of the input metatada.</p></li><li><p>Returns a NetsuiteSoapAttributes object in the output metdata.</p></li></ul></div></div></td></tr><tr><td><p>Get</p></td><td><div><div><ul><li><p>Removed the Base Ref field. You now specify the associated values in the Message field of the input metadata.</p></li><li><p>Returns the requested record in the payload of the output metadata. The playload fields differ based on the specified record type.</p></li></ul></div></div></td></tr><tr><td><p>Get Custom Record</p></td><td><p>Removed this operation. For equivalent functionality, use the Get operation.</p></td></tr><tr><td><p>Get Deleted Records</p></td><td><div><div><ul><li><p>Removed the Record Type, Page Index, and Deleted Date fields. You now specify the associated values in the Message field of the input metatada.</p></li><li><p>Returns a NetsuiteSoapAttributes object in the output metadata.</p></li></ul></div></div></td></tr><tr><td><p>Get List</p></td><td><div><div><ul><li><p>Removed the References field. You now specify the associated values in the Message field of the input metatada.</p></li><li><p>Returns a getListResponse object in the payload of the output metadata.</p></li></ul></div></div></td></tr><tr><td><p>Get Record</p></td><td><p>Removed this operation. For equivalent functionality, use the Get operation.</p></td></tr><tr><td><p>Get Records</p></td><td><p>Returns a NetsuiteSoapAttributes object in the output metadata</p></td></tr><tr><td><p>Get Select Value</p></td><td><p>Returns a getSelectValueResponse object in the payload of the output metadata.</p></td></tr><tr><td><p>Get Saved Search</p></td><td><div><div><ul><li><p>Renamed the Record Type field to <code>Search Type</code>.</p></li><li><p>Returns a NetsuiteSoapAttributes object in the output metadata.</p></li></ul></div></div></td></tr><tr><td><p>Initialize</p></td><td><div><div><ul><li><p>Removed the Record to Initialize field. You now specify the associated values in the Message field of the input metatada.</p></li><li><p>Returns a NetsuiteSoapAttributes object in the output metadata.</p></li></ul></div></div></td></tr><tr><td><p>Initialize List</p></td><td><div><div><ul><li><p>Removed the Initialize Records field. You now specify the associated values in the Message field of the input metatada.</p></li><li><p>Returns a NetsuiteSoapAttributes object in the output metadata.</p></li></ul></div></div></td></tr><tr><td><p>Search</p></td><td><div><div><ul><li><p>Removed the Key and Search Record fields. You now specify the associated values in the Message field of the input metatada.</p></li><li><p>Returns a recordList or searchRowList object in the payload of the output metadata, depending on whether records or rows are searched.</p></li></ul></div></div></td></tr><tr><td><p>Update List</p></td><td><div><div><ul><li><p>Removed the Record Maps field. You now specify the associated values in the Message field of the input metatada.</p></li><li><p>Returns a NetsuiteSoapAttributes object in the output metadata.</p></li></ul></div></div></td></tr><tr><td><p>Update Record</p></td><td><div><div><ul><li><p>Removed the Attributes field. You now specify the associated values in the Message field of the input metatada.</p></li><li><p>Returns a NetsuiteSoapAttributes object in the output metadata.</p></li></ul></div></div></td></tr><tr><td><p>Update Records List</p></td><td><p>Removed this operation. For equivalent functionality, use the Update List operation.</p></td></tr><tr><td><p>Upsert List</p></td><td><div><div><ul><li><p>Removed the Record Maps field. You now specify the associated values in the Message field of the input metatada.</p></li><li><p>Returns a NetsuiteSoapAttributes object in the output metadata.</p></li></ul></div></div></td></tr><tr><td><p>Upsert Record a</p></td><td><div><div><ul><li><p>Renamed the operation to Upsert and removed the Attributes field. You now specify the associated values in the Message field of the input metatada.</p></li><li><p>Returns a NetsuiteSoapAttributes object in the output metadata.</p></li></ul></div></div></td></tr></tbody></table>

## Upgrade Steps

If you are upgrading from an earlier version of the connector, you can click the `Updates Available`
pop-up Message in the bottom right corner of Anypoint Studio and follow the prompts.

You can also follow these steps to perform the upgrade:

1.  In Anypoint Studio, create a Mule project.

2.  In **Mule Palette**, click **Search in Exchange**.

3.  In **Add Dependencies to Project**, enter `netsuite` in the search field.

4.  In **Available modules**, select **NetSuite** and click **Add**.  
    Studio upgrades the connector automatically.

5.  Click **Finish**.

6.  In the `pom.xml` file for the Mule project, verify that the NetSuite Connector dependency
    version is `11.0.0`.

## Post Upgrade Tasks

- Ensure that your configurations use either **Request Based** or **Token** authentication.

- Verify that your error handling is updated to work with the minor changes in error codes in this
  version of the connector.

- Refer to [Changed Operations](#changed_operations) and [Changed Sources](#changed-sources) for
  updated operations and sources.  
  If your integration uses any of the affected operations and sources, make the necessary changes to
  comply with the new interfaces.

- Because the package of the exposed classes was changed to
  `com.mulesoft.connector.netsuite.extension.api`, you must update all DataWeave mappings that
  create objects for operation inputs.  
  You must also update mappings that transform object outputs.

## Verify the Upgrade

After you install the latest version of the connector, verify the upgrade:

1.  In Studio, verify that there are no errors in the **Problems** or **Console** views.

2.  Verify that there are no problems in the project `pom.xml` file.

3.  Test the connection to verify that the operations work.

## Revert the Upgrade

If you must revert to your previous version of NetSuite Connector, change the
`mule-netsuite-connector` dependency version `10.0.0` in the project’s `pom.xml` to the previous
version. Additionally, revert any changes made in the operations to their previous state.

## See Also

[Salesforce Help](https://help.salesforce.com)