Question 1

Which NetSuite records can be written to?

Accepted Answer

Whatever your account exposes, since the list comes from the SuiteTalk REST metadata catalogue rather than being fixed. That covers customers, sales orders, opportunities, contacts, jobs and item records, and includes custom records where they appear in the catalogue and the integration role has access. Create, update, and update or create are offered where NetSuite advertises them. There is no general delete mode.

Question 2

How does a large table behave against NetSuite?

Accepted Answer

It is paced deliberately, and that is the main thing to design around. NetSuite writes are far less warehouse like than other destinations: work is grouped into jobs of at most 100 records, at most five jobs run concurrently per connection, and each record is a separate mutation. Concurrency errors are retried rather than failing the run, so a large backfill queues and completes over time instead of being rejected.

Question 3

How should the data be modelled first?

Accepted Answer

Flat, with one row per record you intend to write. NetSuite expects records with defined fields, so STRUCT, ARRAY and MAP columns need resolving in the model SQL before the mapping stage. Related references can be given as an internal id, an external id, or a reference name, and line item mappings are coalesced into the parent record's payload rather than being sent as separate calls.

Question 4

What sort of data ends up here?

Accepted Answer

It varies by team, but the pattern is usually something modelled centrally that finance or operations need inside their system of record. Order and customer data, usage or subscription detail landing on custom records, and account attributes kept in step all come up. Modelling it in the lakehouse first keeps the logic in one testable place, and runs are differential after the initial backfill so only changes are sent.

Question 5

How do I sync Databricks to NetSuite?

Accepted Answer

Connect Databricks with a SQL warehouse hostname and a token, or an OAuth service principal. NetSuite requires credentials created by an administrator, and the role attached to them decides which records appear, so agree scope with whoever administers the account first. Once connected, model the data flat, choose the record type, map an identity field, and set a schedule that respects the pacing described above.

Connect Databricks with NetSuite

Connect Databricks and NetSuite with Polytomic

Records from your account

Internal or external ID

Paced for NetSuite

Trusted by businesses worldwide

Step-by-step integration guide

Connect Databricks in Polytomic

Connect NetSuite in Polytomic

Create a sync between Databricks and NetSuite

Map fields and enable the sync

Frequently asked questions

The sync and ETL platform that does it all

Powerful data sync

Advanced analytics

Enterprise security

Easy setup

Ready to connect Databricks with NetSuite?