- 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 form types.
- Customizations made to standard fields are honored in SOAP web services. For example, if a standard field is set as disabled, it is not settable through SOAP web services, either. If you try to set such a field through SOAP web services, an error message is returned.
- If a standard field is set to NOT show in the UI, it is not settable through SOAP web services, either. If you try to set such a field through SOAP web services, an error message is returned.
- Custom display only (inline) and disabled fields are not settable through SOAP web services because these are NOT settable through the UI. If you provide a value in your SOAP web services request for such a field, an error message is returned. For information on field display types.
- The behavior of custom hidden fields varies depending on the endpoint being used. If you are using any endpoint since the 2011.2 endpoint (including 2011.2), the get operation does not return the value of custom hidden fields. If you are using an older endpoint, these values are gettable. By comparison, in the UI, these values cannot be seen.
- If you are using the 2011.1 endpoint or earlier, the value of custom hidden fields is returned regardless of the setting of the ignoreReadOnlyFields preference.
- Custom hidden fields cannot be set, either in the user interface or using SOAP web services, regardless of the endpoint.
- Defaulted fields that are set to blank on a SOAP web services update will stay blank on update.
- The bodyFieldsOnly request-level preference affects the way formulas on forms are processed. As a result, if the values of custom fields are calculated using formulas, the search might return incorrect results. If the calculated values of formulas are incorrect, set the bodyFieldsOnly preference to false to make sure the correct values are returned.