NetSuite Get Operation through MuleSoft — Part 1

In our last blog we have seen the Introduction to NetSuite System Integration through MuleSoft, Various Benefits of NetSuite System Integration through MuleSoft and a wide range of operation NetSuite connector offers along with configuration setup

In this blog we will see how to perform Get Operation using NetSuite Connector in MuleSoft by taking Customer record as an example.

Business Use-Case:

Here are some examples of how the NetSuite Get connector can be used in MuleSoft:

Order management: You can use the connector to retrieve order data from NetSuite and then use that data to update your e-commerce platform. This can help you to improve order accuracy and speed up the order fulfilment process.

Customer relationship management (CRM): You can use the connector to retrieve customer data from NetSuite and then use that data to update your CRM system. This can help you to provide a better customer experience and improve customer retention.

Financial reporting: You can use the connector to retrieve financial data from NetSuite and then use that data to generate financial reports. This can help you to save time and improve the accuracy of your financial reporting.

Get Operation:

The get operation is used to retrieve a record by providing the unique id (NetSuite Internal Id) that identifies that record. Let’s demonstrate the NetSuite Get operation with a simple POC.

In the Get-customer-flow as shown in the screenshot, NetSuite Get Connector retrieves a customer record from a list based on the NetSuite internalId provided.

First, set up a HTTP Listener with a path and configure connection. and then add a NetSuite Get connector into the flow. In the Get connector, there will be two drop-down lists (Ref type and Type), in Ref types, select the nature of the record, whether it is a custom record or a record given by NetSuite i.e.RecordRef, in the second one selects the list from which we retrieve the record (it is Customer in the above example flow).

Then add a Transform message before the Get connector and metadata will be generated automatically.

Select internalId and specify the internalId of the record to retrieve, xsi schema needs to be defined in the code to make the operation work as shown in the below screenshot

And at the end of the flow add a Transform message and convert the output to JSON. Once the flow is triggered, NetSuite Get Connector will fetch the details for the given internal Id.

Conclusion

In this blog, we have seen how to perform Get Operation using NetSuite connector in MuleSoft.