You have basic knowledge on how to write in the JSON format and how to parse it to extract
values.

You have knowledge on how to call SOAP/REST Web services with token and Oauth based
authentication.

Job designs to explore few possibilities using Talend NetSuite components

Reading customer entity from NetSuite Portal

This example will show how to connect to NetSuite and read data from the customer entity
type from NetSuite.

The following Job uses the tNetSuiteConnection and
tNetSuiteInput components to read the data out of the NetSuite system. For
more information on how to configure the tNetSuiteConnection component, see
tNetsuiteConnection.

In this example , the Record Type is set to
Customers, and the Search Conditions are set to
look for a customer record with the name UVW Customer.

The tNetsuiteInput component will populate its schema from the
Record Type parameter by connecting to NetSuite and retrieving the schema
details.

Below is a snapshot of the input data with a pipe (|) as column separator.
Some of the column values which are sublist items are appearing as JSON
payloads mapped to string datatype columns. Since the component does not provide
implementation for these columns appearing as JSON, they are mapped as
strings.

Examples of sublists are illustrated in the below picture, like
addressBookList, Sales > Opportunities or Sales > Items Purchased. A sublist is a list that makes up part of a larger list.

Reading and parsing addresses from customers

The job below demonstrates reading data from the Customer Entity and parsing the
Addresses JSON payload and writing the data to a flat file.

The tJavaRow component is used to Set the globalMap
with InternalId so that it can later be used to set the column in the
tMap before persisting it to the file.

As a result, the JSON payload has been converted to a flat structure and
stored into a file. You can also see InternalIds for individual
Address records, as well as Customer Entity. These
internal ids are required during the update operations if there is a need to update any
records.

Inserting a customer entity

In the below example, a process is created to insert a new customer in
NetSuite.

The idea is to read the input data from flat files and convert them to
JSON payloads before sending the data to the
tNetSuiteOutput component. The tNetSuiteOutput components
will structure the data to fit the payload that the NetSuite services is expecting. This is the
reason why a good understanding of the JSON structure for various sublists
is important. Here, both the Address and Subsidiary
strings need to be built in JSON payloads before being merged to a
pipedelimited format needed to call the webservice. The Address also has a
Country picklist that can be updated, and for which the format is
“_greece” or “_india” for example. The
Subsidiary is a pre-existing reference value within NetSuite, hence we
need to send the InternalId to associate it with the
customer entity.