NetSuite SuiteAnalytics

NetSuite provides SuiteAnalytics as a paid option, giving businesses the power of built-in real-time dashboards, reporting and analysis — integrated right into the ERP, CRM, or ecommerce application that you use every day.

Supported data sources

Our NetSuite SuiteAnalytics connector supports the following NetSuite data sources:

• NetSuite2.com
• NetSuite.com

Features

Features for the NetSuite.com data source

* History mode is currently in Private Preview for this connector.

Features for the NetSuite2.com data source

* History mode is currently in Private Preview for this connector.

Supported deployment models

We support the SaaS and Hybrid deployment models for the connector.

Setup guide

Follow our step-by-step NetSuite SuiteAnalytics setup guide to connect NetSuite SuiteAnalytics with your destination using Fivetran connectors.

To set up your NetSuite SuiteAnalytics connection for the NetSuite2.com data source, do the following steps as shown in the tutorial below:

Schema information

NetSuite SuiteAnalytics' schema follows Fivetran's standard API schema rules.

We name the source schema as netsuite and name the destination schema after the schema name set by the user in the setup form.

Using Fivetran you can access the following data sources:

• NetSuite.com – Fivetran currently supports all tables in version 2021.2 as well as any custom tables present in your NetSuite account. See NetSuite's Connect Browser documentation for information on all the available tables, and the domain diagrams illustrating how tables relate to one another.

• NetSuite2.com – Uses the schema that has been used in SuiteAnalytics Workbook since 2019.1. The details about the record types in NetSuite2.com, also known as the analytics data source, are available through the Records Catalog. For more information about the schema, see NetSuite's documentation.

Initial sync

When you first connect a new account, Fivetran scans every table you selected and copies every row for which we have permission to view. We set up multiple concurrent connections to your NetSuite SuiteAnalytics account and retrieve your data from the source tables.

The initial sync can take a while, depending on the number and size of tables to be imported.

Updating data

Fivetran uses one of the following strategies to update the tables that you included in your sync:

Incremental

For the NetSuite.com data source, we update a table incrementally only if it contains:

• a numeric primary key
• a date_last_modified, date_last_modified_gmt, or last_modified_date column

For the NetSuite2.com data source, we update a table incrementally only if it contains:

• a numeric primary key
• a lastmodified, lastmodifieddate, or linelastmodifieddate column

The System_notes and System_notes_custom tables

System_notes and system _notes_custom are audit tables that should be immutable (unchanged). New records are synced incrementally using the date_created column. Updates or deletes are not captured.

The SystemNote table

SystemNote is an audit table that should be immutable (unchanged). New records are synced incrementally using the date column. Updates or deletes are not captured.

Re-import

We need to re-import the table in full if it does not contain:

• a numeric primary key
• one of the timestamp columns

By default, we update these re-import tables based on how fast we can ingest them from NetSuite, which is entirely dependent on NetSuite performance. We use this strategy to maintain the speed of overall updates. However, you can override the default sync frequency and include these tables in every sync. To include them in every sync, set the Re-sync re-import tables during every sync toggle in the connection setup form to ON.

We mark the tables that take longer than 20 seconds to import as not recommended in the dashboard and include a message on how frequently Fivetran syncs them.

* NOTE: The re-import lists above may not be complete as NetSuite is highly configurable, and there may be more or fewer re-import tables for your NetSuite account depending on its configuration.

The TRANSACTION_TRACKING_NUMBERS table

We re-import the TRANSACTION_TRACKING_NUMBERS table twice daily if the table import duration is more than 20 seconds. If the import duration is less than or equal to 20 seconds, we re-import the table in every sync.

The Item_location_map and Posting_Account_Activity tables

We re-import the Item_location_map and Posting_Account_Activity tables in every sync. If it takes too long to re-import these tables, we recommend that you configure another NetSuite SuiteAnalytics connection specifically for these two tables so that there is no impact on the overall performance of the connection.

Duplicate Primary Key value tables

We have observed that many tables in NetSuite contain duplicate values for the primary key column. For such tables, we add the fivetran_index system column to the primary key. The fivetran_index column is a sequential number unique for each primary key value.

Excluded Tables

Excluded tables for the NetSuite.com data source

Excluded tables for the NetSuite2.com data source

Primary Key Hashing

Some primary key columns contain null, but contain at least one non-null primary key column; and most destinations don't support a null value for the primary key column. So, Fivetran creates hash of primary key columns and stores them in the _fivetran_id system column, where the _fivetran_id column is the part of primary key for the table alongside the non-null primary key column. Actual primary key columns won't be created as primary keys of the table in the destination.

Deleting data

We do not rely on the Delete_records table to capture deletes for standard tables. Instead, we use a novel approach to incrementally capture deletes. We logically divide the table into contiguous chunks, and import the chunks for which we detect change (using the checksums from the previous sync). We use the chunk size in a way that it minimises the amount of data to be transferred from NetSuite.

Deleting data for the NetSuite.com data source

1. The following tables have a _fivetran_deleted column in the destination. When rows are deleted from these tables in the account, the corresponding rows in the destination are marked as deleted.

   Expand for the full list of tables with the `_fivetran_deleted` column

   Table Name
   Accounting_books
   Accounts
   Address_book
   Addresses
   Bill_of_distributions
   Billing_accounts
   Billing_rate_cards
   Billing_subscription_lines
   Billing_subscriptions
   Campaign_audiences
   Campaign_categories
   Campaign_families
   Campaign_search_engine
   Campaign_subscriptions
   Campaign_verticals
   Campaignchannel
   Campaignoffer
   Campaigns
   Caseissue
   Caseorigin
   Casetype
   Classes
   Commissionplan
   Company_status
   Competitor
   Contactrole
   Contacts
   Crmtemplate
   Currencies
   Currency_exchange_rate_types
   Currency_exchange_rates
   Currencyrates
   Customer_types
   Customers
   Departments
   Distribution_categories
   Distribution_networks
   Employee_time
   Employees
   Entity
   Entity_status
   Expense_accounts
   Expense_amortization_rules
   Expense_plans
   Global_account_map
   Global_inventory_relationships
   Income_accounts
   Inventory_cost_template
   Item_account_map
   Item_revisions
   Items
   Locations
   Message
   Mfg_cost_template
   Nexus
   Notes_user
   Notetype
   Originating_leads
   Partner_sales_roles
   Partners
   Payment_methods
   Payment_terms
   Payroll_items
   Planned_standard_costs
   Price_types
   Project_revenues_rules
   Promotion_codes
   Purchase_charge_rules
   Resource_groups
   Revenue_elements
   Revenue_plans
   Revenue_recognition_rules
   Sales_reps
   Sales_roles
   Sales_territories
   Service_items
   Subscription_change_orders
   Subscription_plans
   Subsidiaries
   Support_incidents
   Support_territories
   Tax_items
   Territory
   Transactions
   Units_type
   Unlocked_time_periods
   Uom
   Vendors
   Winlossreason

2. Deleted records are hard deleted from the destination for the following tables:

   Expand for the full list of hard-deleted tables

   Table Name
   Accounting_periods
   Activities
   Billing_rate_cards_versions
   Calls
   Campaign_subscription_statuses
   Charges
   Companies
   Companycontactmap
   Contact_types
   Customer_partner_sales_teams
   Customer_sales_teams
   Events1
   Expense_plan_lines
   Fair_value_prices
   Generic_resources
   Gift_certificates
   Inventory_items
   Inventory_number
   Item_billing_rates
   Item_demand_plans
   Item_fulfillments
   Item_supply_plans
   Mfg_routing
   Opportunities
   Opportunity_lines
   Opportunitycontactmap
   Other_names
   Partner_types
   Project_tasks
   Resource_allocations
   Revenue_plan_lines
   Roles1
   Shipping_items
   Solution
   Subscription_line_revisions
   Support_reps
   Tasks
   Timesheet
   Trans_partner_sales_teams
   Transaction_address
   Transaction_line_book_map
   Transaction_lines
   Transaction_links
   Transaction_sales_teams

3. Custom tables with a single primary key also receive entries in the Deleted_records. Therefore, they also have a _fivetran_deleted column in the destination.

4. Re-imported tables also have a _fivetran_deleted column in the destination. After each re-import, any row that no longer exists in the source table is marked as deleted in the destination.

Syncing empty tables and columns

Fivetran can sync empty tables and columns for your NetSuite SuiteAnalytics connection. For more information, see our Features documentation.

Supported data types

Fivetran supports following data types for the NetSuite SuiteAnalytics connector: