10.07.2015 Views

SuiteTalk (Web Services) Platform Guide - NetSuite

SuiteTalk (Web Services) Platform Guide - NetSuite

SuiteTalk (Web Services) Platform Guide - NetSuite

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Records, Fields, Forms, and Sublists in <strong>Web</strong> <strong>Services</strong>Working with Fields in <strong>Web</strong> <strong>Services</strong>53TypeWsEnumListDescriptionCorresponds to a specific type defined as an enum in the XSD that represents systemconstants that are NOT available in the UI.A List references a type that is a list and should be explicitly defined in the in the XMLSchema as a type. A list can either be null (if it’s an optional field), or it must contain atleast one entry unless otherwise noted.Custom fields are those that have been created by <strong>NetSuite</strong> users to customize their accounts.Custom fields can be added to an account using SuiteBuilder point-and-click customizationtools. They can also be added through the <strong>SuiteTalk</strong> add operation. Custom fields must be oneof the types defined in Custom Field Types. Note that on business records, custom fields arecontained in the customFieldList property. For more details, see CustomFieldList.Also note that if you are getting unusual results in your <strong>Web</strong> services queries, it may be that astandard field has been customized. Additionally, a record can have any number of customfields that may differ in their behavior when manipulated through <strong>Web</strong> services, versus whenthey are manipulated through the <strong>NetSuite</strong> UI.The following are some general guidelines to consider when working with both standard andcustom fields.• Regardless of whether a standard field is set as mandatory in a custom form, the“requiredness” of the field is the same as it was originally (entry forms only --transaction forms honor custom requiredness settings). For more information on<strong>NetSuite</strong> form types, see Custom Forms in the <strong>NetSuite</strong> Help Center.• Customizations made to standard fields are not honored in <strong>Web</strong> services. The fieldbehaves as it would with no customization done. For example, even if a standard fieldis set as disabled, it is still settable via <strong>Web</strong> services.• If a standard field is set to NOT show in the UI, it is still settable via <strong>Web</strong> services. Inthe UI, these fields are not settable although the values are returned in search results.• Custom display only (inline) and disabled fields are settable even though these areNOT settable through the UI. For information on field display types, see SettingDisplay Options for Custom Fields in the <strong>NetSuite</strong> Help Center.• Custom hidden fields are gettable and settable in <strong>Web</strong> services. In the UI, customfields defined as hidden are not settable and are not returned.• Defaulted fields that are set to blank on a <strong>Web</strong> services update will stay blank onupdate.Note: If you are unfamiliar with <strong>NetSuite</strong> custom fields, it is recommended that you seeCustom Fields in the <strong>NetSuite</strong> Help Center. This section describes the purpose andgeneral characteristics of each custom field type, which will help you when workingwith the <strong>SuiteTalk</strong> customization API (described in Customization in the <strong>NetSuite</strong>Help Center).<strong>SuiteTalk</strong> <strong>Platform</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!