Skip to main content
Use netsuite in twins and put this configuration under seed_config.netsuite. Oracle NetSuite ERP account with customers, vendors, employees, subsidiaries, chart-of-account records, products and services, sales orders, invoices, customer payments, purchase orders, vendor bills and payments, journal entries, SuiteQL, REST records, RESTlets, and OAuth credentials.

Example seed

This is the complete Scenario request body for creating a Scenario. You can also import it with arga test-runner scenarios import --file scenario.json.

Parameters

The following fields belong directly inside seed_config.netsuite. Required nested fields are marked in their tables. Provider-native objects can contain service-specific fields beyond the representative record shapes below.

Seeding behavior

Resource aliases must reference earlier declared records in the supported seed order. Use {"$ref":"alias.id"} or the supported relationship shortcuts. The configured account ID must match the twin gateway account (TSTDRV1234567).

Resource fields

These tables describe the record shapes used by the example. Keep native field names and casing. Map keys such as property names, IDs, and metadata keys are supplied by your fixture.

subsidiaries[]

accounts[]

customers[]

vendors[]

service_items[]

invoices[]

invoices[].item.items[]

vendor_bills[]

vendor_bills[].expense.items[]

See Scenario seeding for saving, provisioning, and resetting fixtures.