ANS-1478 · WEB SERVICES & INTEGRATIONS

How to Retrieve Transaction Line and Joint Custom Record Fields from NetSuite in Boomi

Leverage NetSuite saved searches and Boomi's NetSuite connector to extract complex data structures, including custom fields from joined records and transaction line items.

Short answer

To retrieve transaction line and joint custom record fields in Boomi, create a NetSuite saved search and configure the Boomi NetSuite connector's QUERY operation. Import the response profile, test, and reimport the XML result. Add Identifier Instances for customSearchJoin elements using the scriptId attribute to correctly map and distinguish custom fields.

Scenario

Users often encounter challenges when attempting to extract complex data from NetSuite into Boomi, specifically when dealing with transaction line items or custom fields from custom records that are joined to standard NetSuite records. The standard Boomi NetSuite connector may not directly expose these fields, requiring an advanced approach to ensure all necessary data is retrieved.

Solution

While not always ideal, a NetSuite saved search can be effectively utilized to access joint custom record fields and transaction line items within Boomi. The following steps outline the process:

  1. Create the necessary saved search within NetSuite.

  2. In the Boomi NetSuite connector's QUERY operation, when importing the profile via the Import Wizard, ensure the 'Use Advanced Saved Search' checkbox is enabled.

  3. Supply the saved search's internal ID to the savedSearchScriptId parameter. If no fields are selected under the Fields tab, the returning fields (search columns) will be defined by your saved search. However, selecting specific fields in Boomi's 'Fields' tab will override the saved search's defined columns, returning only those chosen fields.

  4. Import the response profile directly from NetSuite. Note that the initially imported profile may not contain the desired custom fields or column fields.

  5. Execute a test run of the Boomi process and download the XML result of the saved search to a local drive.

  6. Reimport the downloaded XML file into your query response profile.

  7. Once the XML profile has been imported, if your saved search includes more than one custom record table join, multiple customSearchJoin elements will be visible in your XML profile.

  8. Add an Identifier Instance for each of the joined table elements. The scriptId attribute of the customizationRef element under customSearchJoin can be used for this purpose, as it represents the custom field's internal ID.

  9. Transaction line fields will be returned within the basic > customFieldList structure. Custom fields of joint custom records will be returned within the customSearchJoin element, typically with the element name 'customField'. An identifier instance can also be added using scriptId to distinguish between these fields as needed.

Expert NetSuite Support

Need help with this NetSuite issue?

Web Services & Integrations consulting and configuration support

Talk to a consultant