| java.lang.Object | |
| ↳ | org.mule.module.netsuite.NetSuiteCloudConnector |
Known Direct Subclasses
|
Known Indirect Subclasses
|
The NetSuite cloud connector facade, based on a NetSuiteClient
| Constants | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| String | SUITETALK_LIVE_ADDRESS | ||||||||||
| Fields | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| account | SuiteTalk -NetSuite WebService - account id. | ||||||||||
| client | The Netsuite client to use. | ||||||||||
| The login email of both NetSuite UI and SuiteTalk | |||||||||||
| endpoint | Service endpoint
|
||||||||||
| password | The login password of both the NetSuite UI and SuiteTalk | ||||||||||
| roleId | The id of the role used to login in SuiteTalk, which determines the Processor privileges | ||||||||||
| Public Constructors | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Public Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Answers the server time, resulting in more accurate and reliable sync'ing of data than using
using local client time.
| |||||||||||
Creates a new file record.
| |||||||||||
Used to add one or more records into the system
| |||||||||||
Creates a new record.
| |||||||||||
Searches for all records that match the given filtering expression, asynchronously.
| |||||||||||
Attaches a source record - that is, the attachment - to another destination one,
optionally specifying a contact for the
attachment.
| |||||||||||
Answers the status of an asynchronous Web services submission.
| |||||||||||
Used to delete one or more records in the system.
| |||||||||||
Deletes a record.
| |||||||||||
Detaches a source record - that is, the attachment - from a destination record.
| |||||||||||
Answers the first records that match the given filtering expression.
| |||||||||||
Answers all records that match the given filtering expression.
| |||||||||||
Answers the the first result of an asynchronous asyncFind.
| |||||||||||
Answers the results of an asynchronous web services submission.
| |||||||||||
Answers the list of budget exchange rates
Example:
| |||||||||||
Answers the list of consolidated exchange rates
Example:
| |||||||||||
Answers the ids of available customizations for a given record type.
| |||||||||||
Answers a list of deleted records of a given record type that match a given date expression.
| |||||||||||
Answers the availability for a given record reference.
| |||||||||||
Answers a record given its id
Example:
| |||||||||||
Answers all the record of a given type
Example:
| |||||||||||
Retrieves a list of existing saved searches for the given record type.
| |||||||||||
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:
| |||||||||||
Answers all records of a given type for a saved search, given its search id.
| |||||||||||
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.
| |||||||||||
Updates an existing record.
| |||||||||||
|
[Expand]
Inherited Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
From class
java.lang.Object
| |||||||||||
SuiteTalk -NetSuite WebService - account id. It looks like TSTDRVXXXXXX
The Netsuite client to use. Mainly for mocking purposes
The login email of both NetSuite UI and SuiteTalk
Service endpoint
The login password of both the NetSuite UI and SuiteTalk
The id of the role used to login in SuiteTalk, which determines the Processor privileges
Answers the server time, resulting in more accurate and reliable sync'ing of data than using using local client time. Example:
Creates a new file record. This Processor is similar to addRecord, but is customized for simplifying local content passing.
| attributes | The additional file attributes |
|---|---|
| content | The content of the file record to add. It can be of type String, byte array, File or InputStream. If it is an input stream, this Processors also closes it. |
| fileName | The name of the remote file |
| folderId | The id of the folder record where to add this file |
| folderIdType | The id type of the folder record |
| IOException |
|---|
Used to add one or more records into the system
| recordType | The type of record to add |
|---|---|
| records | The records with their attributes, as a string-object map |
WriteResponseList with the server response
| Exception |
|---|
Creates a new record. Example:
| recordType | The type of record to add |
|---|---|
| attributes | The record attributes, as a string-object map |
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:
| recordType | The type of record to search |
|---|---|
| expression | The filtering expression, 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. Multiple filters can be combined using multiple predicates separated by commas. |
| Exception |
|---|
Attaches a source record - that is, the attachment - to another destination one, optionally specifying a contact for the attachment. Not all record type are supported as source, destination or contact. Please consult NetSuite documentation. Example:
| sourceRecordType | The type of the target record to be attached |
|---|---|
| sourceId | The id of the target record to be attached |
| sourceIdType | The id type of the record to be attached |
| destinationRecordType | The type of the record to be attached to |
| destinationId | The id of the record to be attached to |
| destinationIdType | The id type of the record to be attached to |
| contanctRecordType | The record type of the optional contact record |
| contanctId | The id of the optional contact record |
| contanctIdType | The id type of the optional contact record |
Answers the status of an asynchronous Web services submission. When a jobId is submitted, the status, percent complete, and estimated remaining duration are returned. Example:
| jobId | The id of the job whose status to check |
|---|
Used to delete one or more records in the system. The records to be deleted are identified through the provided unique identifiers.
| records | The records with their attributes, as a string-object map |
|---|
WriteResponseList with the server response
| Exception |
|---|
Deletes a record. Not all records can be deleted. Please consult NetSuite documentation Example:
| recordType | The type of the record to delete |
|---|---|
| id | The id of the record to delete |
| idType | The type of id of the record to delete |
Detaches a source record - that is, the attachment - from a destination record. Example:
| sourceRecordType | The type of the target record to be detached |
|---|---|
| sourceId | The id of the target record to be detached |
| sourceIdType | The id type of the record to be detached |
| destinationRecordType | The type of the record to be detached to |
| destinationId | The id of the record to be detached to |
| destinationIdType | The id type of the record to be detached to |
Answers the first records that match the given filtering expression. If no expression is specified, the empty expression is used, which retrieves all records of the given type. Throws a NoSuchElementException if no record can be 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:
| recordType | The type of record to search |
|---|---|
| expression | The filtering expression Multiple filters can be combined using multiple predicates separated by commas. |
Answers all records that match the given filtering expression. If no expression is specified, the empty expression is used, which retrieves all records of the given type. 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:
| recordType | The type of record to search |
|---|---|
| expression | The filtering expression Multiple filters can be combined using multiple predicates separated by commas. |
Answers the the first result of an asynchronous asyncFind. Throws a NoSuchElement exception if there are no results. 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:
| jobId | The id of the job |
|---|
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:
| jobId | The id of the job |
|---|
Answers the list of budget exchange rates Example:
| periodId | The id of the period |
|---|---|
| periodIdType | The period id type |
| fromSubsidiaryId | The id of the staring subsidiary |
| fromSubsidiaryIdType | The starting subsidiary id type |
| toSubsidiaryId | The the id of the optional ending subsidiary |
| toSubsidiaryIdType | The id type of the optional ending subsidiary |
Answers the list of consolidated exchange rates Example:
| periodId | The id of the period |
|---|---|
| periodIdType | The period id type |
| fromSubsidiaryId | The id of the staring subsidiary |
| fromSubsidiaryIdType | The starting subsidiary id type |
| toSubsidiaryId | The the id of the optional ending subsidiary |
| toSubsidiaryIdType | The id type of the optional ending subsidiary |
Answers the ids of available customizations for a given record type. Example:
| type | The target record type |
|---|---|
| includeInactives | If inactive customizations should also be returned |
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:
| type | The type of the target deleted record to retrieve |
|---|---|
| whenExpression | A predicate-style date filtering expression |
| date1 | The first date to use |
| date2 | The second date to use |
| operator | The date operator |
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. Example:
| recordType | The target record type |
|---|---|
| id | The target record id |
| idType | The id type of the given record id |
| ifModifiedSince | An optional modified since date. If set, only items with quantity available changes recorded as of the specified date are returned. |
Answers a record given its id Example:
| recordType | The target record type |
|---|---|
| id | The target record id |
| idType | The id type of the given record id |
Answers all the record of a given type Example:
| type | The target record type |
|---|
Retrieves a list of existing saved searches for the given record type. Example:
| type | The target record type |
|---|
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:
| type | The type of record whose defaults values are used to populate the target record |
|---|---|
| recordType | The target record type |
| id | The target record id |
| idType | The id type of the given record id |
Answers all records of a given type for a saved search, given its search id. Examples:
| recordType | The type of record to search |
|---|---|
| searchId | The id of the save search |
| account |
|---|
| endpoint |
|---|
| password |
|---|
| roleId |
|---|
Sets a new invitation status for a given event. Example: Example:
| eventId | The target event id |
|---|---|
| eventIdType | The id type of the given eventId |
| status | The new status to set |
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.
| recordType | The type of record to add |
|---|---|
| records | The records with their attributes, as a string-object map |
WriteResponseList with the server response
| Exception |
|---|
Updates an existing record. Example:
| recordType | The target record type to update |
|---|---|
| id | The target record id |
| idType | The id type of the given record id |
| attributes | The record attributes, as a string-object map |
| Exception |
|---|