Company-Wide Preferences
You can set company-wide preferences for SOAP web services. These changes apply to all users.
You can set these preferences at Setup > Integration > SOAP Web Services Preferences.
Some of these preferences can be overridden when you send individual SOAP web services requests. For details, see One-Time Preferences. Note that more preferences are available for individual requests.
The SOAP Web Services Preferences page shows whether concurrency governance is enabled and the available limit for your account. For information about web services and RESTlet concurrency governance, see Web Services and RESTlet Concurrency Governance
Company-wide preferences include:
Disable Mandatory Custom Field Validation
This preference impacts mandatory custom fields in the UI. Setting this to true makes the fields are not required during SOAP web services requests. Setting this to false makes the fields required. Omitting required values returns a USER_ERROR with instructions to provide value for the field.
When deciding whether to enable this preference, consider if the provided data comes from a system that equivalent fields to the custom field.
This preference can be overridden at the request level. For details, see disableMandatoryCustomFieldValidation.
Run Server SuiteScript and Trigger Workflows
This preference applies company-wide. However, you can overwrite this preference in each SOAP web services request. For details, see Request-Level Preferences.
This preference enables server SuiteScripts and triggers workflows and is selected by default. If this preference is not selected, all SuiteScript scripts and workflows are disabled.
Disabling this option has two effects:
-
Disable server SuiteScripts that otherwise would have been triggered by SOAP web services requests.
-
Disable workflows that otherwise would have been triggered by SOAP web services requests.
When importing historical data into NetSuite, consider disabling this option for faster processing and block executions of additional logic performed automatically by executed scripts and workflows. For live data sync or partner apps like Outlook Sync, use the default option, Server. In other words, consider enabling server SuiteScript to run your business logic for integrated apps. Note that enabling server SuiteScript may negatively affect performance.
To ensure that your business logic is fully executed, always use the default option, Server. Additionally, changing the default option can potentially break your working integration. Avoid this unless you're an advanced SOAP web services user.
Require Approval During Auto-Installation of Integration
Auto-installation creates an integration record in your NetSuite account automatically. For instance, a partner may provide you with an updated version of an application. This update may include a new application ID created by using an integration record. The first time you send a request using this application, a new integration record is created in your account.
The Require Approval during Auto-Installation of Integration determines if the new record is enabled automatically. If set to false, the State field on the new application is set to Enabled, and requests are allowed. If set to true, the Set field on the new integration record is set to Waiting for Approval. You must then manually set the state to Enabled. Until enabled, all requests from the application are blocked.
Search Page Size
The Search Page Size preference controls the number of returned search results. It applies to both synchronous and asynchronous searches. Company-wide, valid values range from 5 to 1,000. The default value is 1,000.
You can override this preference for individual searches. For individual searches, asynchronous searches have a higher maximum than the company-wide limit. For more details, see pageSize.
Treat Warnings as Errors
Enabling this preference treats warning messages generated by NetSuite as errors that cause an exeption, rejecting the request. For more information about the difference between errors and warnings, see SOAP Web Services Warnings, Errors, and Faults.
This preference can be overridden per request. For details, see warningAsError.