NetSuiteCloudConnector

The Netsuite client to use. Mainly for mocking purposes

The login email of both NetSuite UI and SuiteTalk

Service endpoint

Supports:
• Live: https://webservices.netsuite.com/services/NetSuitePort_2013_2
• Sandbox: https://webservices.sandbox.netsuite.com/services/NetSuitePort_2013_2

Creates a new file record.

This Processor is similar to addRecord, but is customized for simplifying local content passing.

Used to add one or more records into the system

Creates a new record.

Creates new records

An asynchronous requests equivalent to addRecord(String, Map, Preferences).

In asynchronous requests, your client application sends a request to the SuiteTalk Platform where it is placed in a processing queue and handled asynchronously with other requests. Note that all available jobs for each polling period will be processed contiguously. There is no enforced waiting period for a job that is available. Once a job is processed, a job ID is returned in the Web services response. Your client application can then check on the status and result of the request by referencing the job ID.

Note: Asynchronous request JobIDs are valid for 30 days.

An asynchronous requests equivalent to #deleteList(Map).

In asynchronous requests, your client application sends a request to the SuiteTalk Platform where it is placed in a processing queue and handled asynchronously with other requests. Note that all available jobs for each polling period will be processed contiguously. There is no enforced waiting period for a job that is available. Once a job is processed, a job ID is returned in the Web services response. Your client application can then check on the status and result of the request by referencing the job ID.

Note: Asynchronous request JobIDs are valid for 30 days.

An asynchronous requests equivalent to #deleteList(Map).

In asynchronous requests, your client application sends a request to the SuiteTalk Platform where it is placed in a processing queue and handled asynchronously with other requests. Note that all available jobs for each polling period will be processed contiguously. There is no enforced waiting period for a job that is available. Once a job is processed, a job ID is returned in the Web services response. Your client application can then check on the status and result of the request by referencing the job ID.

Note: Asynchronous request JobIDs are valid for 30 days.

An asynchronous requests equivalent to #getList(Map).

In asynchronous requests, your client application sends a request to the SuiteTalk Platform where it is placed in a processing queue and handled asynchronously with other requests. Note that all available jobs for each polling period will be processed contiguously. There is no enforced waiting period for a job that is available. Once a job is processed, a job ID is returned in the Web services response. Your client application can then check on the status and result of the request by referencing the job ID.

Note: Asynchronous request JobIDs are valid for 30 days.

An asynchronous requests equivalent to #getList(Map).

In asynchronous requests, your client application sends a request to the SuiteTalk Platform where it is placed in a processing queue and handled asynchronously with other requests. Note that all available jobs for each polling period will be processed contiguously. There is no enforced waiting period for a job that is available. Once a job is processed, a job ID is returned in the Web services response. Your client application can then check on the status and result of the request by referencing the job ID.

Note: Asynchronous request JobIDs are valid for 30 days.

An asynchronous requests equivalent to #initializeRecord.

In asynchronous requests, your client application sends a request to the SuiteTalk Platform where it is placed in a processing queue and handled asynchronously with other requests. Note that all available jobs for each polling period will be processed contiguously. There is no enforced waiting period for a job that is available. Once a job is processed, a job ID is returned in the Web services response. Your client application can then check on the status and result of the request by referencing the job ID.

Note: Asynchronous request JobIDs are valid for 30 days.

Searches for all records that match the given filtering expression, asynchronously.

If no expression is specified, all records of the given type are retrieved

Filtering expressions support both basic and joined syntax, that is, using in the filters attributes of both the target entity and the target entity associations. Advanced search is not supported.

Search expressions are in the form operator(attribute, arguments...) for basic search, and operator(join.attribute, arguments...) for joined search, where operator is any of the string, long, double, and text operators supported by SuiteTalk - MultiSelect operators are not supported - plus the isTrue/isFalse boolean operators, and arguments are zero up to three operands that depend on the operator used.

Examples:

An asynchronous requests equivalent to #updateRecord(Map).

In asynchronous requests, your client application sends a request to the SuiteTalk Platform where it is placed in a processing queue and handled asynchronously with other requests. Note that all available jobs for each polling period will be processed contiguously. There is no enforced waiting period for a job that is available. Once a job is processed, a job ID is returned in the Web services response. Your client application can then check on the status and result of the request by referencing the job ID.

Note: Asynchronous request JobIDs are valid for 30 days.

An asynchronous requests equivalent to #upsertRecord(Map).

In asynchronous requests, your client application sends a request to the SuiteTalk Platform where it is placed in a processing queue and handled asynchronously with other requests. Note that all available jobs for each polling period will be processed contiguously. There is no enforced waiting period for a job that is available. Once a job is processed, a job ID is returned in the Web services response. Your client application can then check on the status and result of the request by referencing the job ID.

Note: Asynchronous request JobIDs are valid for 30 days.

Attaches a source or contact record - that is, the attachment - to another destination one

Not all record type are supported as source, destination or contact. Please consult NetSuite documentation.

Use to change the email address for the account.

Use to change the password for the account.

Answers the status of an asynchronous Web services submission.

When a jobId is submitted, the status, percent complete, and estimated remaining duration are returned.

Connection Management connect method

Deletes a record. Not all records can be deleted. Please consult NetSuite documentation

Used to delete one or more records in the system. The records to be deleted are identified through the provided unique identifiers.

Deletes a record. Not all records can be deleted. Please consult NetSuite documentation

Used to delete one or more records in the system. The records to be deleted are identified through the provided unique identifiers.

Detaches a source record - that is, the attachment - from a destination record.

Connection Management disconnect method

This is used to retrieve a record by providing the unique id that identifies that record.

Answers the results of an asynchronous web services submission.

This Processor can be executed Processor up to 20 times within a 30 day time period to retrieve the results of an asynchronous job.

Example:

Answers the list of budget exchange rates

Answers the list of consolidated exchange rates

Use this operation to get the exchange rate between two currencies based on a certain date.

Answers the ids of available customizations for a given record type.

Use for dynamic discovery of data-center-specific URLs for partner applications’ access to NetSuite.

Answers a list of deleted records of a given record type that match a given date expression.

This Processors accepts two different date expression passing styles: string oriented, and object oriented. If whenExpression is specified, it is parsed and used as date expression. Otherwise, a date expression is build from date1, date2 and operator parameters.

The first style is more appropriate when the date expression can be harcdoded, while the second style is better when client code already has date objects. However, predefined search values like thisWeek, tomorrow or today can only be used with the first, string oriented, style.

String oriented date expressions are in the form Processor( searchValue, arguments...), where Processor is any of the NetSuite supported date Processors, arguments are one or two operands for the given operator, and searchValue is some of the supported predefined search value as defined by NetSuite or any of the following expressions:

• isoDate( anIsoDate ), isoDateRante( anIsoDate, anotherIsoDate )
• dateTime( aQuotedDateTime, aQuoatedJavaDateFormat )
• dateTimeRange( aQuotedDateTime, anotherQuotedDateTime, aQuoatedJavaDateFormat )

Supported predefined search values are:

• today
• thisWeek
• thisBusinessWeek
• thisMonth
• thisYear
• yesterday
• twoDaysAgo
• lastWeek
• lastMonth
• threeMonthAgo
• tomorrow
• nextMonth
• nextWeek

Examples using both string and object oriented styles:

Answers the availability for a given record reference.

If the Multi-Location Inventory feature is enabled, this Processor returns results for all locations.

For locations that do not have any items available, only location IDs and names are listed in results.

This operation is used to retrieve a list of objects referenced in the list of BaseRef object.

Use to retrieve a summary of the actual data in an account.

The getPostingTransactionSummary operation allows you to retrieve a summary of the actual data that posted to the general ledger in an account. You can use available filters/fields to generate reports that are similar to what you see when you run financial reports such as a Trial Balance, Balance Sheet, or an Income Statement.

This is used to retrieve a record by providing the unique id that identifies that record.

This operation is used to retrieve a list of all records of the specified type. Records that support the getAll operation are listed in the GetAllRecordType

Retrieves a list of existing saved searches for the given record type.

Use to retrieve valid values for a given recordRef field where the referenced record type is not yet exposed in the Web services API or when the logged in role does not have permission to the instances of the record type.

Answers the server time, resulting in more accurate and reliable sync'ing of data than using using local client time.

Populates fields on transaction line items with values from a related record, in a similar way empty text boxes are prepopulated within the Netsuite UI

Example:

Use to emulate the UI workflow by pre-populating fields on transaction line items with values from a related record. The initializeList operation can be used to run batch processes to retrieve initialized records.

Use to automate the mapping between external applications credentials and NetSuite’s credentials for a user.

This operation provides mapping, not a login to NetSuite. This operation does NOT provide the ability to log in using a single sign-on token, cannot provisian a partner with the inbound single sign-on feature, or aid with public/private key exchange. Use of this operation implies that the account already has inbound single sign-on set up and has access to the associated partner ID and encryption keys needed to generate the token.

Return a list of records, or columns matching the query provided. You can also use the #queryRecords( String,boolean,Integer) queryRecords if you want direct access to the records as Maps.

Take into account that netsuite Record models doesn't match the models they use for search, so user will probably want to write some of the query by hand.

Return a list of records. This should only be used when you want to retrieve all the columns.

Take into account that netsuite Record models doesn't match the models they use for search, so user will probably want to write some of the query by hand.

The search operation is used to execute a search on a specific record type based on a set of criteria.

You can search by defining search filter fields on the record, joined fields on an associated record, search return columns, or joined search return columns from an associated record. The results of the search can be complete records, or a select set of fields specified through search return columns.

The seachMore operation is used to retrieve more records after an initial search operation.

The results returned in a searchMore operation reflect the records in the next segment as defined in the original search operation.

The searchMoreWithId operation allows users to reference a specific search result set by its searchId, a parameter included in all search results.

As with searchMore, users must set the pageIndex value to specify which page in the search to return.

The searchNext operation is used to retrieve the next set of records after an initial search operation.

The search operation is used to execute a search on a specific record type based on a set of criteria.

You can search by defining search filter fields on the record, joined fields on an associated record, search return columns, or joined search return columns from an associated record. The results of the search can be complete records, or a select set of fields specified through search return columns.

Use to establish a single sign-on connection.

This operation allows for a partner application to login on behalf of the user in to NetSuite, without the user’s credentials ever going through partner servers.

Updates existing record's custom fields.

Sets a new invitation status for a given event.

Sets a new invitation status for a given event.

Used to update one or more existing records in the system by providing new values for the fields to be updated for each record. The records to be updated are identified through the provided unique identifiers.

Updates an existing record.

Used to update one or more existing records in the system by providing a list of records. The records to be updated are identified through the provided unique identifiers.

NOTE: This call cannot be used with Data mapping or data sense, it was added to allow users to add a batch of records of any type in 1 call.

The upsertList operation is used to add or update one or more instances of a record type in NetSuite.

The upsertList operation is similar to both the addList and updateList operations, but upsert can be run without first determining whether records exist in NetSuite. Records are identified by their external ID and their record type. If a record of the specified type with a matching external ID exists in the system, it is updated. If it does not exist, a new record is created.

Because external ID is mandatory for this operation, upsertList is supported only for records that support the external ID field.

Also, this operation prohibits the passing of internal ID values.

The upsert operation is used to add a new instance or to update an instance of a record in NetSuite.

It is similar to the upsertList operation, which allows users to add or update more than one record at a time. The upsert operation is similar to both the add and update operations, but upsert can be run without first determining whether a record exists in NetSuite. A record is identified by its external ID and its record type. If a record of the specified type with a matching external ID exists in the system, it is updated. If it does not exist, a new record is created.

Because external ID is mandatory for this operation, upsert is supported only for records that support the external ID field.

Also, this operation prohibits the passing of internal ID values.