# Salesforce NetSuite Integration App expectations for subsidiaries and pricebooks

**URL:** <https://connective.celigo.com/t/salesforce-netsuite-integration-app-expectations-for-subsidiaries-and-pricebooks/6092>\
**Category:** Integration Apps\
**Tags:** salesforce, netsuite\
**Created:** [February 24, 2026, 10:28pm UTC](https://connective.celigo.com/t/salesforce-netsuite-integration-app-expectations-for-subsidiaries-and-pricebooks/6092 "2026-02-24T22:28:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![AlexP](https://avatars.discourse-cdn.com/v4/letter/a/e9a140/32.png) [@AlexP](https://connective.celigo.com/u/AlexP)\
**Post date:** [February 24, 2026, 10:28pm UTC](https://connective.celigo.com/t/salesforce-netsuite-integration-app-expectations-for-subsidiaries-and-pricebooks/6092/1 "2026-02-24T22:28:17Z")

</div>

Hi all — I’ve opened support tickets on both of these, but I’m still not clear on the intended/“supported” approach with the out-of-the-box Salesforce/NetSuite Integration App (IO) flows. Hoping someone here has run into the same scenarios.

### 1) Salesforce Account → NetSuite Customer (multi-subsidiary Customer)

We’re using a multi-subsidiary NetSuite setup. For the standard SF Account → NS Customer flow, is there a supported way to assign _all subsidiaries_ to the Customer (i.e., primary + one or more secondary subsidiaries)?

Celigo docs don’t seem to address this use case. Primary subsidiary - sure, no problem. I tried mapping multiple _secondary_ subsidiaries by having each secondary subsidiary be carried via its own mapping to `Subsidiaries : Subsidiary (InternalId)` field. When the flow runs, it doesn’t throw an error, but only one secondary subsidiary appears to get applied in NetSuite.

If multi-subsidiary assignment is supported, could someone share the recommended mapping pattern?

### 2) NetSuite Item → Salesforce Product (PricebookEntry updates)

This one is more worrisome in that we expected this to work out of the box without resorting to support tickets. The out-of-the-box NS Item → SF Product flow seems to create a `PricebookEntry`, but I can’t get it to **update** an existing `PricebookEntry`.

When I use Preview, the REST request being generated looks like it’s targeting the Product, but updating `PricebookEntry` typically requires a different request pattern (and often a lookup by Product + Pricebook). I may be missing a standard setting or pattern here, but I haven’t found documentation that explains how the Integration App expects PricebookEntry maintenance to work (especially for updates). And yes, I have Standard pricebook mapped in Settings.

If anyone has a working configuration for updating PricebookEntry as part of the Item → Product sync (or knows whether this is outside the Integration App’s intended scope), I’d really appreciate any guidance.

Thanks in advance — even a “yes, supported / no, requires customization” would help set expectations.

---

<div class="post-metadata">

**Author:** ![kalyandusanapudi43](https://avatars.discourse-cdn.com/v4/letter/k/97f17d/32.png) [@kalyandusanapudi43](https://connective.celigo.com/u/kalyandusanapudi43)\
**Post date:** [March 5, 2026, 12:16pm UTC](https://connective.celigo.com/t/salesforce-netsuite-integration-app-expectations-for-subsidiaries-and-pricebooks/6092/2 "2026-03-05T12:16:26Z")

</div>

### Salesforce Account → NetSuite Customer (Multi-Subsidiary)

At this time, syncing multiple secondary subsidiaries in a single execution is not supported.

The flow supports:

- One primary subsidiary

- One secondary subsidiary

If multiple subsidiary mappings are added, they overwrite each other because the flow and underlying script expect a single value, not an array. Iteration or array-based mapping is not currently supported in the standard flow.

The Multi-Subsidiary feature flag (MULTISUBSIDIARYCUSTOMER) must be enabled in the NetSuite account

### NetSuite Item → Salesforce Product (PricebookEntry Updates)

Updating existing **PricebookEntry** records is supported out of the box.

The flow:

- Checks for an existing PricebookEntry before import

- Updates it if found

- Creates a new one only if no match exists

- Uses Salesforce Composite API (Product + PricebookEntries together)

If updates are not occurring, the most common causes are:

- Missing NetSuite Price Level → Salesforce Pricebook mapping

- Standard Pricebook not configured or refreshed

- Product ID mismatch between NetSuite and Salesforce

- Currency mapping gaps (if multi-currency is enabled)