LogoLogo
  • 🦩Overview
  • 💾Datasets
    • Overview
    • Core Concepts
      • Columns & Annotations
      • Type & Property Mappings
      • Relationships
    • Basic Datasets
      • dbt Integration
      • Sigma Integration
      • Looker Integration
    • SaaS Datasets
    • CSV Datasets
    • Streaming Datasets
    • Entity Resolution
    • AI Columns
      • AI Prompts Recipe Book
    • Enrichment Columns
      • Quick Start
      • HTTP Request Enrichments
    • Computed Columns
    • Version Control
  • 📫Syncs
    • Overview
    • Triggering & Scheduling
    • Retry Handling
    • Live Syncs
    • Audience Syncs
    • Observability
      • Current Sync Run Overview
      • Sync History
      • Sync Tracking
      • API Inspector
      • Sync Alerts
      • Observability Lake
      • Datadog Integration
      • Warehouse Writeback
      • Sync Lifecycle Webhooks
      • Sync Dry Runs
    • Structuring Data
      • Liquid Templates
      • Event Syncs
      • Arrays and Nested Objects
  • 👥Audience Hub
    • Overview
    • Creating Segments
      • Segment Priorities
      • Warehouse-Managed Audiences
    • Experiments and Analysis
      • Audience Match Rates
    • Activating Segments
    • Calculated Columns
    • Data Preparation
      • Profile Explorer
      • Exclusion Lists
  • 🧮Data Sources
    • Overview
    • Available Sources
      • Amazon Athena
      • Amazon Redshift
      • Amazon S3
      • Azure Synapse
      • ClickHouse
      • Confluent Cloud
      • Databricks
      • Elasticsearch
      • Kafka
      • Google AlloyDB
      • Google BigQuery
      • Google Cloud SQL for PostgreSQL
      • Google Pub/Sub
      • Google Sheets
      • Greenplum
      • HTTP Request
      • HubSpot
      • Materialize
      • Microsoft Fabric
      • MotherDuck
      • MySQL
      • PostgreSQL
      • Rockset
      • Salesforce
      • SingleStore
      • Snowflake
      • SQL Server
      • Trino
  • 🛫Destinations
    • Overview
    • Available Destinations
      • Accredible
      • ActiveCampaign
      • Adobe Target
      • Aha
      • Airship
      • Airtable
      • Algolia
      • Amazon Ads DSP (AMC)
      • Amazon DynamoDB
      • Amazon EventBridge
      • Amazon Pinpoint
      • Amazon Redshift
      • Amazon S3
      • Amplitude
      • Anaplan
      • Antavo
      • Appcues
      • Apollo
      • Asana
      • AskNicely
      • Attentive
      • Attio
      • Autopilot Journeys
      • Azure Blob Storage
      • Box
      • Bloomreach
      • Blackhawk
      • Braze
      • Brevo (formerly Sendinblue)
      • Campaign Monitor
      • Canny
      • Channable
      • Chargebee
      • Chargify
      • ChartMogul
      • ChatGPT Retrieval Plugin
      • Chattermill
      • ChurnZero
      • CJ Affiliate
      • CleverTap
      • ClickUp
      • Constant Contact
      • Courier
      • Criteo
      • Crowd.dev
      • Customer.io
      • Databricks
      • Delighted
      • Discord
      • Drift
      • Drip
      • Eagle Eye
      • Emarsys
      • Enterpret
      • Elasticsearch
      • Facebook Ads
      • Facebook Product Catalog
      • Freshdesk
      • Freshsales
      • Front
      • FullStory
      • Gainsight
      • GitHub
      • GitLab
      • Gladly
      • Google Ads
        • Customer Match Lists (Audiences)
        • Offline Conversions
      • Google AlloyDB
      • Google Analytics 4
      • Google BigQuery
      • Google Campaign Manager 360
      • Google Cloud Storage
      • Google Datastore
      • Google Display & Video 360
      • Google Drive
      • Google Search Ads 360
      • Google Sheets
      • Heap.io
      • Help Scout
      • HTTP Request
      • HubSpot
      • Impact
      • Insider
      • Insightly
      • Intercom
      • Iterable
      • Jira
      • Kafka
      • Kevel
      • Klaviyo
      • Kustomer
      • Labelbox
      • LaunchDarkly
      • LinkedIn
      • LiveIntent
      • Loops
      • Mailchimp
      • Mailchimp Transactional (Mandrill)
      • Mailgun
      • Marketo
      • Meilisearch
      • Microsoft Advertising
      • Microsoft Dynamics
      • Microsoft SQL Server
      • Microsoft Teams
      • Mixpanel
      • MoEngage
      • Mongo DB
      • mParticle
      • MySQL
      • NetSuite
      • Notion
      • OneSignal
      • Optimizely
      • Oracle Database
      • Oracle Eloqua
      • Oracle Fusion
      • Oracle Responsys
      • Orbit
      • Ortto
      • Outreach
      • Pardot
      • Partnerstack
      • Pendo
      • Pinterest
      • Pipedrive
      • Planhat
      • PostgreSQL
      • PostHog
      • Postscript
      • Productboard
      • Qualtrics
      • Radar
      • Reddit Ads
      • Rokt
      • RollWorks
      • Sailthru
      • Salesforce
      • Salesforce Commerce Cloud
      • Salesforce Marketing Cloud
      • Salesloft
      • Segment
      • SendGrid
      • Sense
      • SFTP
      • Shopify
      • Singular
      • Slack
      • Snapchat
      • Snowflake
      • Split
      • Sprig
      • Stripe
      • The Trade Desk
      • TikTok
      • Totango
      • Userflow
      • Userpilot
      • Vero Cloud
      • Vitally
      • Webhooks
      • Webflow
      • X Ads (formerly Twitter Ads)
      • Yahoo Ads (DSP)
      • Zendesk
      • Zoho CRM
      • Zuora
    • Custom & Partner Destinations
  • 📎Misc
    • Credits
    • Census Embedded
    • Data Storage
      • Census Store
        • Query Census Store from Snowflake
      • General Object Storage
      • Bring Your Own Bucket
        • Bring your own S3 Bucket
        • Bring your own GCS Bucket
        • Bring your own Azure Bucket
    • Developers
      • GitLink
      • Dataset API
      • Custom Destination API
      • Management API
    • Security & Privacy
      • Login & SSO Settings
      • Workspaces
      • Role-based Access Controls
      • Network Access Controls
      • SIEM Log Forwarding
      • Secure Storage of Customer Credentials
      • Digital Markets Act (DMA) Consent for Ad Platforms
    • Health and Usage Reporting
      • Workspace Homepage
      • Product Usage Dashboard
      • Observability Toolkit
      • Alerts
    • FAQs
Powered by GitBook
On this page
  • Getting Started
  • Prerequisites
  • 1. Create an Integration Record for Census
  • 2. Enable Token Based Authentication
  • 3. Create a Token Role
  • 4. Add Token Management Permissions
  • 5. Create Access Tokens
  • 6. One more thing: NetSuite Account ID
  • 7. Finally, Configure Your Census Connection
  • Sync Speed
  • ️ Supported Objects
  • Supported Sync Behaviors
  • ❓Netsuite Quirks
  • Need help connecting to NetSuite?

Was this helpful?

  1. Destinations
  2. Available Destinations

NetSuite

This page describes how to use Census with NetSuite.

PreviousMySQLNextNotion

Last updated 2 months ago

Was this helpful?

Getting Started

In this guide, we will show you how to connect NetSuite to Census and create your first sync.

Prerequisites

  • Have your NetSuite account ready, with the Administrator role.

  • Have the proper credentials to access to your data source. See our docs for each supported data source for further information:

1. Create an Integration Record for Census

  1. Visit the integrations page or use the global search to look for and navigate to: page: Manage Integrations

  1. Create a new integration with the follow properties:

    • Give it a name that you'll recognize, such as Census

    • Check TOKEN-BASED AUTHENTICATION

    • Leave OAuth 2.0 AUTHORIZATION CODE GRANT unchecked

    • Leave TBA: AUTHORIZATION FLOW unchecked

    • Set State to Enabled

  2. Click Save when finished.

  3. Copy and paste the CONSUMER KEY / CLIENT ID and CONSUMER SECRET / CLIENT SECRET to a password manager. You'll need those later to paste into Census.

2. Enable Token Based Authentication

  1. Global search to page: Enable Features

  2. Navigate to the tab SuiteCloud > Manage Authentication

  3. Make sure Token Based Authentication is checked

  4. Save

3. Create a Token Role

The Administrator user you're using with NetSuite and Census also needs "Token Role".

  1. Global search to page: New Role

  2. Name the role: Census

  3. Check WEB SERVICES ONLY ROLE

  4. Check DO NOT RESTRICT EMPLOYEE FIELDS

  5. For multi-subsidiary NetSuite users**,** check ALL under ACCESSIBLE SUBSIDIARIES

  6. Under Permissions > Setup, add the following permissions:

    • Access Token Management: Full

    • Custom Body Fields: Full

    • Custom Column Fields: Full

    • Custom Entity Fields: Full

    • Custom Fields: Full

    • Custom Item Fields: Full

    • SOAP Web Services: Full

    • REST Web Services: Full

    • User Access Token: Full

7. Under Permissions > Lists, Give your Role the appropriate permissions for the NetSuite objects you'll be updating. For example, to update Customers, you'll want to give this role the Lists > Customers (Full) permission.

4. Add Token Management Permissions

  1. Global search to page: Employees

  2. Edit the employee record of the Admin user you will be using Census with.

  3. Navigate to Access > Roles and add the Token Role you just created above.

5. Create Access Tokens

  1. Global search to page: Access Tokens

  2. Click New Access Token

  3. Select the application and role we created above, then press Save

  4. Copy and paste the new Token ID and Token Secret to your password manager or file. We'll use it below.

Note: Netsuite permission changes to a role or user do not occur immediately. These changes typically take anywhere from a few minutes to a few hours, and they can even take up to 24 hours to go into effect. If you are confident that you have given Census the correct permissions above and experience an error setting up the connection, we recommend waiting for these changes to go into effect before testing the connection again.

6. One more thing: NetSuite Account ID

The last bit of information you’ll need is your NetSuite Account ID:

  1. Global search to page: Company Information.

  2. Your ACCOUNT ID will be found on that page. Copy and paste it as well.

7. Finally, Configure Your Census Connection

  1. Now in Census, add a new Destination.

  1. Paste the Account ID of your NetSuite Account, as well as the Consumer Key, Consumer Secret, Token ID and Token Secret created above.

  1. Click Save Connection, and click Test to double check your connection information.

You're ready to start using Census to load data from your warehouse to NetSuite! If you have any trouble with these steps, please don't hesitate to reach out to: support@getcensus.com and we'll help get this setup.

Sync Speed

NetSuite's API speed and rate limitation are complex and are tied to the plan you are on but you can expect a speed of ~500 records sync / minute on their base plan,

Service

Records sync / Minute

NetSuite

500

️ Supported Objects

Object Name

Supported?

Account

✅

Billing Account

✅

Cash Sale

✅

Class

✅

Contact

✅

Credit Memo

✅

Currency

✅

Customer

✅

Customer Deposit

✅

Customer Payment

✅

Customer Refund

✅

Customer Status

✅

Custom Record

✅

Department

✅

Employee

✅

Invoice

✅

Inventory Item

✅

Inventory Adjustment

✅

Item Fulfillment

✅

Item Receipt

✅

Journal Entry

✅

Location

✅

Other Charge Item

✅

Partner

✅

Purchase Order

✅

Sales Order

✅

Subscription

✅

Subscription Change Order

✅

Subsidiary

✅

Vendor

✅

Vendor Bill

✅

Supported Sync Behaviors

Behaviors

Supported?

Objects

Update or Create

✅

All

Update Only

✅

All

Create Only

✅

All

❓Netsuite Quirks

Netsuite is one of our most complex destinations, and some objects have behavior that is not explained in the Netsuite docs. Here are some known quirks to be aware of:

Customer Payment

  • The Account field cannot be set on record creation; it can only be set on record update

  • In order to change a Customer Payment status to "Deposited", you must send a record update that both sets the Undep Funds (short for "undeposted funds") field to false, and sets the Account field to the bank account into which the funds were deposited.

Invoice

  • If you're syncing to the Item List on the Invoice object your Item List data will need to be formatted in a JSON array like the following example.[{"amount": 2.5, "item": {"internalId": "13"}, "quantity": 1}] .

Using TranId as a Sync Key

  • In order to sync to the TranId field, Allowed Override will need to be checked for the Document Numbers of the object.

  • Example: Setup > Company > Auto-Generated Numbers > Document Numbers > Journal

Need help connecting to NetSuite?

Have your Census account ready. If you need one, now.

This process involves several steps - please set aside 15-30 minutes to complete it. NetSuite configuration can be complex, so if you have any questions please via support@getcensus.com and we'll help you tailor these instructions to your needs.

Please note that you can contact your Customer Success Manager at NetSuite to increase your NetSuite to increase the records sync speed.

This is is the current list of NetSuite supported by our destination. There are many more and we add them on a case by case basis. If you need a different type of object, please contact us to let us know which object do you need, and we will be happy to support it.

Please note that NetSuite doesn't support the via Census and currently we don't support feature for NetSuite

Learn more about all of our sync behaviors in our documentation.

if you want Census to support more Sync Behaviors for this destination

For more information on the Invoice schema please visit

For more information on Auto Generated Numbers please visit the

For more information on all Netsuite Objects and their fields please visit

via support@getcensus.com or start a conversation with us via the chat.

🛫
create a Free Trial Census account
contact us
Azure Synapse
Databricks
Elasticsearch
Google BigQuery
Google Sheets
MySQL
Postgres
Redshift
Snowflake
SQL Server
account API concurrency
objects
creation of fields
add all fields
Syncs
📫
Contact us
Netsuite's Schema Browser
Netsuite Help Center
Netsuite's Schema Browser
Contact us
in-app