Tag: soap_webservices

The upsert operation adds a new instance or updates an instance of a record in NetSuite. It is similar to the upsertList operation, which allows users to add or update more than one record at a time. The upsert operation is similar to both the add and update operations, but upsert can be run without… Continue reading upsert operation in SOAP WEBSERVICES

To check the status of an asynchronous SOAP web services job, you use the checkAsyncStatus operation. When you use this operation, you reference a job Id. In response, the system returns the job’s status, among other details. Specific status values that can be returned include the following: failed finishedWithErrors — indicates that at least one… Continue reading Fetching the Asynchronous Job status

Auto-installation can be used with integration records that are configured to authenticate through user credentials, token-based authentication or OAuth 2.0. Whether using The Three-Step TBA Authorization Flow, calling The IssueToken Endpoint, or using OAuth 2.0, an Integration record is automatically installed in your account. The Require Approval during Auto-Installation of Integration preference affects whether this record is automatically… Continue reading Integration Records Installation via SOAP

The SOAP web services feature must be enabled prior to submitting SOAP web services requests. To enable the SOAP web services feature: As administrator, click Setup > Company > Enable Features. Click the SuiteCloud subtab. Check the SOAP Web Services box. Click Save. Note that after you have enabled SOAP web services in your NetSuite account, you should set your SOAP… Continue reading Enabling the SOAP Web Services Feature

Preferences, customizations, and custom fields are cached by SOAP web services sessions, in Create, Read, Update, Delete and search operations. For example, if you enable or disable an accounting preference at  Setup > Accounting > Preferences > Accounting Preferences, your current SOAP web services session still retains the previous setting of the preference. To have… Continue reading SOAP Cache clearing time for the preferences

The available preferences are: disableMandatoryCustomFieldValidation disableSystemNotesForCustomFields ignoreReadOnlyFields runServerSuiteScriptAndWorkflowTriggers warningAsError bodyFieldsOnly pageSize returnSearchColumns

If a standard field is set as mandatory in a custom form, the “requiredness” of the field is honored in SOAP web services. If you do not provide value in your SOAP web services request for a field that is set as mandatory in a custom form, an error message is returned. For more information on NetSuite… Continue reading SOAP guidelines when working with both standard and custom fields

When certain conditions are met, a user can auto-install an integration record into a NetSuite account or account by sending a SOAP web services request to the target account. With auto-installation users have some control over the value of the State field on newly installed records. The initial value of this field is set according… Continue reading How to create Integration record via SOAP Auto-Installation

Matrix sublists respect the replaceAll attribute for updates, as other Keyed Sublists do, but in some cases, updates to matrix sublists require additional handling. Matrix sublists require additional handling for replaceAll because body-level fields populate values into them. For example, setting the pricing schedule for an item dictates values in the pricing matrix. In the UI, when… Continue reading Updating Matrix Sublists in SOAP Web Services