NetSuite SuiteAnalytics Connect ODBC Setup and Troubleshooting Checklist
This checklist walks through setting up NetSuite SuiteAnalytics Connect over ODBC or JDBC, from licensing and role permissions to driver install and DSN values. The last group covers the failures admins see most often when Excel, Power BI or a warehouse cannot connect.
0 of 33 items complete
7 critical items still open - these are the highest-risk gaps.
Licensing and feature
Role and user
Driver install
DSN configuration
Troubleshooting
Most failed Connect setups trace to a critical item: wrong data source, blocked port 1708, wrong driver bitness or a role without record permissions.
Get your Connect setup checked
Send us your DSN settings (without passwords) and role permissions and we will tell you what is blocking the connection or slowing the refresh.
Optional. The tool and every export work without this. No spam.
How to use it
Start at the top even if the driver is already installed: many broken connections are a role problem, not a driver problem. Work through licensing and the role with the NetSuite administrator, then hand the driver and DSN groups to whoever owns the client machine or BI gateway. Use the troubleshooting group as a diagnostic list when a working connection stops. Tick items as you confirm them and export the list with the role ID, driver version and DSN name filled in your notes, so the next person does not have to rediscover them.
Where the settings live
The feature is on the Analytics subtab of Enable Features. The driver download page opens from the Set Up SuiteAnalytics Connect link in the Settings portlet on the Home dashboard, and the page also shows the service host, port, account ID and role ID values for the logged-in user and role, which is the quickest way to get them right. The ODBC DSN is created in the Windows ODBC Data Source Administrator (64-bit or 32-bit to match the client) or in odbc.ini on Linux. Table and column names for NetSuite2.com are documented in the Records Catalog, under Setup in recent releases, which is the reference to use instead of guessing from old SQL.
Worked example
A controller cannot see the transaction table in Power BI. The DSN uses 1234567.connect.api.netsuite.com on port 1708 with NetSuite2.com, so the host and data source are right. Test Connection succeeds, which rules out the firewall. The custom role has the SuiteAnalytics Connect permission but only Lists permissions, so NetSuite2.com hides every transaction table. The admin adds view permissions for the transaction types the report needs, the controller reconnects, and the table appears. The second issue, slow refresh, is fixed by filtering the query on lastmodifieddate for the last 35 days and appending to the existing dataset rather than reloading years of lines.
Version differences and gotchas
NetSuite.com is the older Connect data source; NetSuite2.com uses the same record and field model as SuiteQL and is the one to build on. Queries written for one do not run on the other unchanged. Driver releases follow NetSuite releases, so keep a note of which driver each gateway uses. Bitness mismatches show up as a DSN that exists in one ODBC administrator but is invisible to the application. Read All and the Data Warehouse Integrator role give broad access, which is convenient for a warehouse and risky for a desktop user, so treat them as privileged.
Frequently Asked Questions
Where do I download the NetSuite ODBC driver?
Log in with a role that has the SuiteAnalytics Connect permission and use the Set Up SuiteAnalytics Connect link in the Settings portlet on the Home dashboard. The page offers ODBC drivers for Windows and Linux, the JDBC driver and ADO.NET, and shows your service host, port, account ID and role ID.
Do I need the 64-bit or 32-bit NetSuite ODBC driver?
Match the application, not Windows. 64-bit Excel and Power BI Desktop need the 64-bit driver and a DSN created in the 64-bit ODBC Data Source Administrator. 32-bit Office needs the 32-bit driver. If a DSN is missing in the application, the usual cause is a bitness mismatch.
Why are tables missing in my NetSuite ODBC schema?
With NetSuite2.com, the schema you see depends on the role in the RoleID property. If the role lacks permission for a record type, its tables are not shown. Add the permission, or use a role with SuiteAnalytics Connect - Read All where that is appropriate, then reconnect.
Can I use the NetSuite ODBC driver on Linux?
Yes. NetSuite provides a Linux ODBC driver. Install the unixODBC driver manager first, then the NetSuite driver, register it in odbcinst.ini and define the DSN in odbc.ini with the same host, port 1708, NetSuite2.com data source and AccountID and RoleID properties used on Windows. JDBC is another option for Java-based tools.
If you want people to ask NetSuite questions in plain English over a private connection on your own infrastructure, instead of building every report in Excel, we can set that up.
Related Tools
NetSuite Saved Search vs Report vs SuiteQL vs Workbook Assessment
Score your reporting need on joins, volume, delivery, users and integration to see whether a saved search, workbook, SuiteQL or SuiteAnalytics Connect fits best.
NetSuiteNetSuite Role Permission Matrix Worksheet
An editable worksheet that records which role holds which permission level on each record area and scores the access risk for review.
NetSuiteNetSuite SuiteQL Transaction Query Generator
Pick a transaction type, date range and row limit and get ready-to-run SuiteQL for headers, lines and the REST call that executes it.
NetSuiteNetSuite Administrator Security and 2FA Hardening Checklist
Review NetSuite authentication, roles, integration tokens, login monitoring and data access in one checklist, with the critical controls marked.
More NetSuite tools
See all- NetSuite Saved Search Formula Generator
- NetSuite CSV Import Template Guide
- NetSuite Inventory Costing Method Reference
- NetSuite Month End Close Checklist
- NetSuite License Cost Estimator
- NetSuite User Access Request Form Template
- NetSuite Custom Record Design Spec Template
- NetSuite SuiteScript Deployment Handover Template
- NetSuite Sandbox and Release Change Log Worksheet
Keep exploring
Free tools
- NetSuite SuiteAnalytics Connect ODBC and JDBC Connection String GeneratorEnter your service host, account ID and role ID to get a working JDBC URL, Windows DSN settings, ODBC connection strings, a Linux odbc64.ini stanza and test queries.
- NetSuite Workflow Troubleshooting ChecklistA five-step diagnostic for SuiteFlow workflows that do not initiate, skip actions or behave differently in imports and integrations.
- NetSuite Manufacturing Go-Live ChecklistA 30 item checklist covering data, setup, costing, inventory, roles and cutover before you run production in NetSuite.
ERP fixes and how-tos
- Setting up NetSuite SuiteAnalytics Connect for ODBC and JDBC accessEnable and configure SuiteAnalytics Connect for read-only ODBC/JDBC access to NetSuite from Power BI, Tableau or Excel, including DSN setup, role permissions, and why large joins time out.
- Exporting large volumes of data out of NetSuite reliablyDesign a reliable large-scale NetSuite export: compare SuiteAnalytics Connect, SuiteQL via SuiteTalk REST, saved search CSV export and RESTlet/Map-Reduce pulls, and use lastmodifieddate for incremental sync instead of repeated full loads.
- How to write and run SuiteQL queries in NetSuiteRun SuiteQL from Analytics > SuiteQL Query Tool or via N/query in SuiteScript. Syntax basics, joins, pagination and real examples for NetSuite reporting.
AI on your ERP
- AI for NetSuite, Beyond the Built-In Text ToolsNetSuite's built-in AI covers text generation, not grounded answers on your own data. See how a private LLM over SuiteQL adds real Q&A and controls.
- AI for NetSuite OneWorld Multi-Subsidiary ConsolidationGrounded AI for NetSuite OneWorld consolidation: intercompany, elimination, and multi-subsidiary questions answered through SuiteQL, without sending financial data to a public model.
Integrations
- How to connect Power BI to Oracle NetSuiteConnect Power BI to Oracle NetSuite: SuiteAnalytics Connect ODBC, SuiteQL, a warehouse, gateway setup, manufacturing dashboards and natural-language Q&A.
- How to connect Power BI to JD Edwards WorldConnect Power BI to JD Edwards World on IBM i: ODBC and gateway setup, a staging layer for Julian dates, key manufacturing dashboards, and natural-language Q&A.