Configuring NetSuite Operations

To use the NetSuite connector, add the <netsuite.init> element in your configuration before carrying out any other NetSuite operations. All Web services operations require authentication. The SuiteTalk platform supports two approaches for authentication. One is the authentication approach using the login operation and the other is the authentication approach using the request level credentials. This connector uses authentication with the request-level credentials, which are sent in the SOAP header while maintaining the HTTPS proxy.

init

<netsuite.init>
	<apiUrl>{$ctx:apiUrl}</apiUrl>
    <warningAsError>{$ctx:warningAsError}</warningAsError>
    <disableSystemNotesForCustomFields>{$ctx:disableSystemNotesForCustomFields}</disableSystemNotesForCustomFields>
    <ignoreReadOnlyFields>{$ctx:ignoreReadOnlyFields}</ignoreReadOnlyFields>
    <disableMandatoryCustomFieldValidation>
    {$ctx:disableMandatoryCustomFieldValidation}
    </disableMandatoryCustomFieldValidation>			
    <roleInternalId>{$ctx:roleInternalId}</roleInternalId>
    <partnerId>{$ctx:partnerId}</partnerId>
    <applicationId>{$ctx:applicationId}</applicationId>
    <roleName>{$ctx:roleName}</roleName>
    <password>{$ctx:password}</password>
    <roleExternalId>{$ctx:roleExternalId}</roleExternalId>
    <email>{$ctx:email}</email>
    <account>{$ctx:account}</account>
    <roleType>{$ctx:roleType}</roleType>
    <blocking>false</blocking>
</netsuite.init>

Properties

apiUrl: The API URL of the NetSuite API.
warningAsError: A boolean Preference object element value specifying whether to treat warnings as errors.
disableSystemNotesForCustomFields: A boolean Preference object element value specifying whether to disable system notes for custom fields.
ignoreReadOnlyFields: A boolean Preference object element value specifying whether to ignore read-only fields.
disableMandatoryCustomFieldValidation: A boolean Preference object element value specifying whether to perform mandatory custom field validation.
roleInternalId: The internal ID of the role.
partnerId: The partner ID of the request.
applicationId: The application ID of the request.
roleName: The name of the role.
password: The valid password of the authenticated user.
roleExternalId: The external ID of the role.
email: The email address of the authenticated user.
account: The ID of the authenticated NetSuite account.
roleType: The type of the role.
blocking: Set true to perform the blocking invocations to Netsuite (Support with ESB 4.9.0 onwards).

Additional information

Note

For parameters that take objects, the objects should be defined as in the API documentation. For example, the "records" object in the "addList" method should be named as in the API document, as shown below.

example

<urn:records>
    <platformMsgs:record xmlns:RecordRef="urn:core_2014_1.platform.webservices.netsuite.com" xmlns:listRel="urn:relationships_2014_1.lists.webservices.netsuite.com" xsi:type="listRel:Customer"  xmlns:platformMsgs="urn:messages_2014_1.platform.webservices.netsuite.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<listRel:entityId>Alex De Silva</listRel:entityId>
	<listRel:companyName>Company, Inc</listRel:companyName>
	<listRel:subsidiary>
		<RecordRef:internalId>3</RecordRef:internalId>
		<RecordRef:type>subsidiary</RecordRef:type>
	</listRel:subsidiary>
	</platformMsgs:record>
</urn:records>

Now that you have connected to Netsuite, use the information in the following topics to perform various operations with the connector.