# NetSuite SuiteAnalytics Connect ODBC Setup and Troubleshooting Checklist > Source: https://netray.co/tools/netsuite-suiteanalytics-connect-odbc-setup-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Check licensing, role permissions, driver bitness, DSN settings and the usual failure points when connecting Excel, Power BI or a warehouse to NetSuite over ODBC or JDBC. ## Category netsuite ## Erp NetSuite ## Audience - NetSuite administrator - BI developer - Data engineer ## Tool **Kind:** checklist **Groups:** #### Licensing and feature **Items:** **Text:** Confirm the SuiteAnalytics Connect add-on is licensed for the account **Critical:** true Enable the feature at Setup > Company > Enable Features, Analytics subtab, SuiteAnalytics Connect Decide which environment you are connecting to (production or a sandbox) and note its account ID Agree what the connection is for (ad hoc Excel, scheduled BI refresh, warehouse extract) so you size the role correctly #### Role and user **Items:** Create a dedicated role for Connect rather than reusing Administrator **Text:** Give the role the SuiteAnalytics Connect permission **Critical:** true Add SuiteAnalytics Connect - Read All only if the use case needs all data regardless of other role permissions Consider the Data Warehouse Integrator role for full NetSuite2.com extracts, and restrict who can use it **Text:** Give the role permissions on every record type you need, as NetSuite2.com only shows tables the role can see **Critical:** true Use a dedicated service user and apply your password policy to it Check how the role's 2FA requirement interacts with the authentication method your driver version supports (password or token-based) #### Driver install **Items:** Download the driver from the Set Up SuiteAnalytics Connect link in the Settings portlet on the Home dashboard **Text:** Match driver bitness to the client: 64-bit driver for 64-bit Excel or Power BI Desktop, 32-bit for 32-bit Office **Critical:** true Run the Windows installer as a local administrator If the installer fails, remove older Connect driver versions first and retry, then check the installer log On Linux, install the unixODBC driver manager before the NetSuite driver and register the driver in odbcinst.ini For JDBC, use the current NQjc jar from the download page, not a copy from an old project Record the driver version installed on each machine and gateway #### DSN configuration **Items:** **Text:** Service Host: .connect.api.netsuite.com, with the account ID in lowercase and sandbox suffix such as 1234567-sb1 **Critical:** true **Text:** Service Port: 1708, and allow outbound TCP 1708 through the firewall and any proxy **Critical:** true **Text:** Service Data Source: NetSuite2.com **Critical:** true Custom properties: AccountID=;RoleID= Leave encryption on and remove any old ciphersuites parameter from copied connection strings Use Test Connection in the ODBC Data Source Administrator before opening Excel or Power BI For an on-premises data gateway, configure the same DSN name and driver bitness on the gateway server #### Troubleshooting **Items:** Login fails: check the RoleID is the role's internal ID and the user has that role Tables missing: the role lacks permission on that record type; add it and reconnect Different table names than a colleague: one connection uses the older NetSuite.com data source, the other NetSuite2.com Use the Records Catalog to look up NetSuite2.com table and field names and joins Timeouts on large tables: filter by lastmodifieddate and extract incrementally instead of full loads Errors after a NetSuite release: check whether a newer driver is offered and update it Isolate the problem with a simple query such as SELECT id, tranid FROM transaction on a few rows Check the Login Audit Trail for the Connect user to see the failure reason NetSuite recorded **Scoring Note:** Most failed Connect setups trace to a critical item: wrong data source, blocked port 1708, wrong driver bitness or a role without record permissions. ## Content **Intro:** 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. **Sections:** #### How to use it **Body:** 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 **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### Where do I download the NetSuite ODBC driver? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms netsuite odbc driver 64 bit, netsuite odbc driver download, netsuite suiteanalytics connect odbc driver, netsuite odbc drivers crashing during install, netsuite odbc linux, netsuite odbc schema, netsuite odbc connection, suiteanalytics connect netsuite2.com --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json