How to fetch both Body feilds and line fields of a record in REST Webservices?

REST web services do not automatically expand sublists and subrecords. You can use the expandSubResources query parameter to expand sublists and subrecords. If the query parameter is not used, the response contains only the body fields of the record, and the sublists and subrecords are represented by links. See the example in Getting a Record Instance. The following… Continue reading How to fetch both Body feilds and line fields of a record in REST Webservices?

How to transform records in REST Webservices?

In REST web services, you can transform a record from one type into an another, using data from an existing records. For example, you can create an invoice record from an existing sales order record, using data from the sales order. All record transformations available in SuiteScript are available in REST web services, too. Transformations… Continue reading How to transform records in REST Webservices?

How to create Integration record via SOAP Auto-Installation

When certain conditions are met, a user can auto-install an integration record into a NetSuite account or account by sending a SOAP web services request to the target account. With auto-installation users have some control over the value of the State field on newly installed records. The initial value of this field is set according… Continue reading How to create Integration record via SOAP Auto-Installation

Updating Matrix Sublists in SOAP Web Services

Matrix sublists respect the replaceAll attribute for updates, as other Keyed Sublists do, but in some cases, updates to matrix sublists require additional handling. Matrix sublists require additional handling for replaceAll because body-level fields populate values into them. For example, setting the pricing schedule for an item dictates values in the pricing matrix. In the UI, when… Continue reading Updating Matrix Sublists in SOAP Web Services

Updating Non-keyed Sublists in SOAP Web Services

Non-keyed sublists have no indexing line element or internal ID that can be used as a key. Each line in a non-keyed sublist is recorded in a flat list. In the UI, non-keyed sublists and keyed sublists may look similar; however, technically, they are quite different. Because non-keyed sublists contain no referencing keys (or handles), you cannot… Continue reading Updating Non-keyed Sublists in SOAP Web Services

Updating Keyed Sublists in SOAP Web Services

Keyed sublists have an indexing line element or internal ID that can be used as a key. Keyed sublists allow you to set the replaceAll attribute to FALSE to update only the lines you are submitting in your SOAP request. When working with keyed sublists, the value of the replaceAll attribute has the following effects: replaceAll =… Continue reading Updating Keyed Sublists in SOAP Web Services

Setting up Syncs in Hightouch to use as a NetSuite connector

Syncs declare how you want query results from a model to appear in your destination. To learn more about syncs on a conceptual level, see the core concepts page. Refer to destination docs for specific configuration details. To learn more about the information the Hightouch UI displays on your syncs and what actions you can take… Continue reading Setting up Syncs in Hightouch to use as a NetSuite connector

Setting up new models in Hightouch for BigQuery to NetSuite data transfer (reverseETL)

Hightouch models define and organize the data you want to query from a source. To create a new model, navigate to the Models page and click Add model. Next, select one of you the sources you’ve setup. Then choose a modeling method: SQL editor Table selector dbt model selector Looker Sigma Supported modeling methods depend on the source. Refer to… Continue reading Setting up new models in Hightouch for BigQuery to NetSuite data transfer (reverseETL)