This notice is intended for customers with SOAP web services integrations using disableMandatoryCustomFieldValidation or disableSystemNotesForCustomFields.
You are receiving this notification because a change planned for NetSuite 2027.1 may affect SOAP web services integrations in your account. This change will affect integrations that use either of these preferences: disableMandatoryCustomFieldValidation or disableSystemNotesForCustomFields.
What’s Changing?
Starting with NetSuite 2027.1, these SOAP request preferences will require the permissions listed in the following table. The role used to authenticate the request must have the matching permission at the Full level.
SOAP request preference | Required permission at the Full level |
|---|
disableMandatoryCustomFieldValidation | Control Disable Mandatory Custom Fields in Web Services Request |
disableSystemNotesForCustomFields | Control System Notes on Custom Fields in Web Services Request |
Setting either preference to false will not remove the permission requirement. For disableMandatoryCustomFieldValidation permission will also be required when the value matches the company-wide setting.
If your integration doesn’t need to set a preference for an individual request, you can omit it. When disableMandatoryCustomFieldValidation is omitted, NetSuite will use the company-wide setting.
These requirements will apply across all SOAP endpoints for both synchronous and asynchronous authenticated operations. Without the required permission, the request will fail with an INSUFFICIENT_PERMISSION error. If an asynchronous request fails the permission check, NetSuite won’t create an asynchronous job.
This permission error is separate from USER_EROR, which NetSuite returns when a request omits a required custom field value.
If your integration also uses runServerSuiteScriptAndWorkflowTriggers to disable scripts and workflow triggers, review the role used to authenticate the SOAP request. Check its existing Control SuiteScript and Workflow Triggers in Web Services Request permission at the Full level.
Required Actions
Before your account is upgraded to NetSuite 2027.1, complete the following steps:
- Review your SOAP integrations to identify requests that include either preference and the role used to authenticate them. If a third party manages your integration, contact that provider to coordinate the changes.
- Determine whether your integrations need to set these preferences for individual requests. Remove any unnecessary preference. If you omit disableMandatoryCustomFieldValidation, NetSuite will use the company-wide setting.
- For each preference your integration will continue to include, have an administrator edit the role used to authenticate its SOAP requests. Under Permissions > Setup, add the corresponding permission listed above and set its level to Full. If a required permission is unavailable for the role, contact NetSuite Customer Support.
- Test the updated integrations in your NetSuite 2027.1 Release Preview account when available to verify that requests complete successfully. Confirm that authorized requests succeed and that requests without the required permission return an
INSUFFICIENT_PERMISSION fault.
If you have any questions, please contact NetSuite Customer Support.