SuiteTalk (Web Services) Platform Guide - NetSuite

Web Services OperationsaddList124addList}+ ((RecordRef) response.getBaseRef()).getInternalId()+ "\nentityId="+ customer.getEntityId()+ "\ncompanyName="+ customer.getCompanyName()+ "\nemail="+ customer.getEmail()+ "\nstatusKey="+ customer.getEntityStatus().getInternalId()+ "\naddressbookList[0].label="+ customer.getAddressbookList().getAddressbook(0).getLabel());} else {_console.error("The customer was not added:", true);_console.error(getStatusDetails(response.getStatus()));}The addList operation is used to add one or more new instances of a record to NetSuite. If thereare multiple records, they can either be of the same record type or different record types. Forexample, it’s possible to add a customer and a contact within a single request using thisoperation. However, each record entered must have a unique signature. Adding two recordswith the same signature results in a SOAP fault. The signature consists of parameters requiredto identify a record as unique.For example, in the case of entities, a record is uniquely identified by its name, its type and itsparent hierarchy. So you could have two records with the same entityId (or name) belonging totwo different record types as follows:Customer (the type):John SmithMyCompany: John SmithContactJohn SmithBut a second record such as the following would be invalid:ContactJohn SmithNote: An asynchronous equivalent is available for this operation, asyncAddList. Forinformation about asynchronous request processing, see Synchronous andAsynchronous Request Processing.RequestThe AddListRequest type is used for the request.SuiteTalk Platform Guide