The reference object for this parameter The NetSuite cloud connector facade, based on a Give a name to this configuration so it can be later referenced by config-ref. Service endpoint <ul>Supports: <li>Live: https://webservices.netsuite.com/services/NetSuitePort_2012_1</li> <li>Sandbox: https://webservices.sandbox.netsuite.com/services/NetSuitePort_2012_1</li> </ul> Defaults to Live The login email of both NetSuite UI and SuiteTalk The login password of both the NetSuite UI and SuiteTalk SuiteTalk -NetSuite WebService - account id. It looks like TSTDRVXXXXXX The id of the role used to login in SuiteTalk, which determines the Processor privileges 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: Specify which configuration to use for this invocation. the type of the target record to be attached the id of the target record to be attached the id type of the record to be attached the type of the record to be attached to the id of the record to be attached to the id type of the record to be attached to the record type of the optional contact record the id of the optional contact record the id type of the optional contact record Deletes a record. Not all records can be deleted. Please consult NetSuite documentation Example: Specify which configuration to use for this invocation. the type of the record to delete the id of the record to delete the type of id of the record to delete Detaches a source record - that is, the attachment - from a destination record. Example: Specify which configuration to use for this invocation. the type of the target record to be detached the id of the target record to be detached the id type of the record to be detached the type of the record to be detached to the id of the record to be detached to the id type of the record to be detached to Answers the list of budget exchange rates Example: Specify which configuration to use for this invocation. the id of the period the period id type the id of the staring subsidiary the starting subsidiary id type the the id of the optional ending subsidiary the id type of the optional ending subsidiary Answers the list of consolidated exchange rates Example: Specify which configuration to use for this invocation. the id of the period the period id type the id of the staring subsidiary the starting subsidiary id type the the id of the optional ending subsidiary the id type of the optional ending subsidiary Answers the ids of available customizations for a given record type. Example: Specify which configuration to use for this invocation. the target record type 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: Specify which configuration to use for this invocation. the type of the target deleted record to retrieve a predicate-style date filtering expression the first date to use the second date to use the date operator Answers all the record of a given type Example: Specify which configuration to use for this invocation. the target record type Answers a record given its id Example: Specify which configuration to use for this invocation. the target record type the target record id the id type of the given record id 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: Specify which configuration to use for this invocation. the target record type the target record id the id type of the given record id an optional modified since date. If set, only items with quantity available changes recorded as of the specified date are returned. Retrieves a list of existing saved searches for the given record type. Example: Specify which configuration to use for this invocation. the target record type Answers the server time, resulting in more accurate and reliable sync'ing of data than using using local client time. Example: Specify which configuration to use for this invocation. Sets a new invitation status for a given event. Example: Example: Specify which configuration to use for this invocation. the target event id the id type of the given eventId the new status to set Creates new records Example: The Records object The reference object for this parameter Specify which configuration to use for this invocation. the type of record to add Creates a new record. Example: the record attributes, as a string-object map The reference object for this parameter Specify which configuration to use for this invocation. the type of record to add Used to add one or more records into the system The records with their attributes, as a string-object map The reference object for this parameter The reference object for this parameter Specify which configuration to use for this invocation. the type of record to add 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. The records with their attributes, as a string-object map The reference object for this parameter The reference object for this parameter Specify which configuration to use for this invocation. the type of record to add Used to delete one or more records in the system. The records to be deleted are identified through the provided unique identifiers. The records with their attributes, as a string-object map The reference object for this parameter The reference object for this parameter Specify which configuration to use for this invocation. the type of record to add Creates a new file record. This Processor is similar to addRecord, but is customized for simplifying local content passing. the additional file attributes The reference object for this parameter Specify which configuration to use for this invocation. 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. the name of the remote file the id of the folder record where to add this file the id type of the folder record Updates an existing record. Example: the record attributes, as a string-object map The reference object for this parameter Specify which configuration to use for this invocation. the target record type to update the target record id the id type of the given record id 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. the record attributes, as a string-object map The reference object for this parameter Specify which configuration to use for this invocation. the target record type to update the target record id 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 record attributes, as a string-object map The reference object for this parameter The reference object for this parameter Specify which configuration to use for this invocation. the target record type to update Updates existing record's custom fields Example: the custom fields as a map, where the key is the internalId The reference object for this parameter Specify which configuration to use for this invocation. the target record type to update the type of custom field the target record id the id type of the given record id 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: Specify which configuration to use for this invocation. the id of the job whose status to check 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: Specify which configuration to use for this invocation. the type of record to search the filtering expression Multiple filters can be combined using multiple predicates separated by commas. 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. Returns null if no element 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: Specify which configuration to use for this invocation. the type of record to search the filtering expression Multiple filters can be combined using multiple predicates separated by commas. Answers all records of a given type for a saved search, given its search id. Examples: Specify which configuration to use for this invocation. the type of record to search the id of the save search 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: Specify which configuration to use for this invocation. the type of record to search 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. 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: Specify which configuration to use for this invocation. the id of the job 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: Specify which configuration to use for this invocation. the id of the job 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: Specify which configuration to use for this invocation. the type of record whose defaults values are used to populate the target record the target record type the target record id the id type of the given record id