SuiteTalk Web Services Integration
This release note was updated March 3, 2025.
NetSuite 2025.1 includes the following enhancements to web services features:
REST Web Services Supported Records in 2025.1
In 2025.1, the following records became fully supported in REST web services.
|
Record Type |
Notes |
|---|---|
|
You must enable the Merchandise Hierarchy feature before you can use this record through REST web services. This feature depends on the Custom Segments feature. |
|
|
You must enable the Merchandise Hierarchy feature before you can use this record through REST web services. This feature depends on the Custom Segments feature. |
|
|
You must enable the Merchandise Hierarchy feature before you can use this record through REST web services. This feature depends on the Custom Segments feature. |
For a list of every supported record, see REST Web Services Supported Records.
You can also see the list of supported records in the REST API browser. For more information about working with the browser, see The REST API Browser.
Behavioral Change of 2025.1 Endpoint Regarding Complex Type Elements
Starting with the 2025.1 endpoint, elements of complex type are ordered so that parent complex elements precede elements of given complex type. This means that additional content model particles are added at the end.
The behavior of previous endpoints does not change and additional content model particles remain at the beginning.
SOAP Web Services Version 2025.1
SOAP web services version 2025.1 is not yet available.
When SOAP web services version 2025.1 becomes available, version 2018.1 will be retired.
For information about the supported generally available versions, see Support for Existing WSDL Versions.
Araxis Merge Diff File for the 2025.1 Endpoint
The Araxis Merge diff file highlights the schema changes between the 2024.2 and 2025.1 endpoints.
About the Araxis Merge Diff File
NetSuite publishes an Araxis Merge diff file for every new endpoint. Depending on the scope of the release, changes described in the Araxis Merge diff file may include:
-
New record types
-
Elements (fields) that have been added, removed, or changed
-
New sublists (lists)
-
New joins
-
New search filters and search return columns
-
New platform operations
Using the Araxis Merge Diff File
The screenshots in this section are for illustrative purposes only. They do not reflect changes related to any specific endpoint.
The Araxis Merge diff file is generated using Araxis Merge. When you click the Araxis Merge diff file link (when it is available), a page appears that offers an overview of all schema changes.
The following screenshot shows how this summary page looks. In this example, the highlighted rows indicate that an XSD has been modified. The integers at the center indicate the number of changed lines in the file. To see the exact differences, click the report link in the column on the right or click the name of the file in either column.
When you click any of these links, the Araxis Merge diff file shows a page with two columns. The previous version of the file is displayed on the left and the new version is displayed on the right. Changed elements are highlighted.
For example, the following screenshot shows an excerpt from the report on platform.commonTypes.xsd. Notice the addition of two values to the PermissionCode enumeration: _accessPaymentAuditLog and _advancedPDFHTMLTemplates.
The Araxis Merge diff file also shows changes to data types. The following screenshot is a snapshot of transactions.sales.xsd. Notice that the chargeType element changed from an enumeration to a RecordRef.
2025.1 SOAP Schema Browser
The 2025.1 SOAP Schema Browser is not yet available.