SuiteAnalytics Connect links NetSuite with Power BI, Tableau, Excel, and other reporting tools. It works best for teams that need secure, read-only access to NetSuite data.
Your finance team may export the same NetSuite reports every week. Someone downloads a CSV file, fixes the columns, and rebuilds the same charts. The process takes time and creates room for errors.
SuiteAnalytics Connect can remove many of those manual steps. It lets reporting tools query NetSuite data through an ODBC, JDBC, or ADO.NET driver. Your team can then build reports that refresh on a set schedule.
SuiteAnalytics Connect is NetSuite's official data connection service. It gives outside reporting tools read-only access to NetSuite records.
The service supports three main driver types:
ODBC is common with Power BI, Tableau, and Excel. JDBC is often used with Java tools and data platforms. ADO.NET supports tools built on Microsoft technology.
SuiteAnalytics Connect does not give direct access to NetSuite's main database. Instead, it gives users a supported way to query NetSuite data.
The service uses SuiteQL. SuiteQL is NetSuite's SQL-based query language. It looks much like standard SQL. However, NetSuite controls which records, joins, and functions SuiteQL can use.
The connector is read-only. It cannot create, edit, or delete NetSuite records. That makes it useful for reporting. A dashboard can read invoice data without changing the invoice itself.
SuiteAnalytics Connect now uses the NetSuite2.com data source. Oracle stopped supporting the older NetSuite.com source in 2025.1. Oracle removed the older source with NetSuite 2026.1. New reporting projects should use NetSuite2.com.
NetSuite2.com matches the data model used by SuiteAnalytics Workbook. It also uses NetSuite roles and permissions. This means users should only see records allowed by their assigned role. The exact level of access depends on the role used for the connection.
A custom reporting role can limit access by:
NetSuite also provides the Data Warehouse Integrator role. This role offers broad access for large data transfers.
Use that role with care. It may allow access to far more data than a normal analyst needs.
NetSuite includes several useful reporting tools. Saved Searches and SuiteAnalytics Workbooks handle many daily reporting needs.
Those tools are often the best place to start. They work inside NetSuite and do not require another system.
However, outside BI tools can help with wider reporting needs.
Common examples include:
Power BI and Tableau also offer more chart and dashboard options. Users can filter data, compare periods, and view several measures on one screen.
The goal is not to create prettier charts. The goal is to make useful data easier to access.
Many finance teams follow the same reporting process each month. They export data, clean the file, and update a spreadsheet.
That process may work for years. It may also become hard to manage as the company grows.
A connected report can remove repeated file exports. The BI tool can pull approved NetSuite data on a schedule.
This can also reduce version problems. Leaders no longer need to ask which spreadsheet contains the latest numbers.
However, automation does not fix weak report logic. The report must still use the right fields, dates, and accounting rules.
A dashboard that refreshes each morning can still show the wrong answer. It just shows the wrong answer faster.
Power BI is a common tool for NetSuite reporting. It can connect through the NetSuite ODBC driver.
The setup has several parts. You must enable SuiteAnalytics Connect, install the driver, set permissions, and configure authentication.
Log in to NetSuite with the required administrator access.
Go to:
Setup > Company > Enable Features
Open the Analytics tab. Enable SuiteAnalytics Connect and save the change.
SuiteAnalytics Connect is a separate NetSuite add-on. Contact your NetSuite account manager if the feature is not available.
Open the Settings portlet on the NetSuite homepage. Select the SuiteAnalytics Connect driver download link.
Choose the driver for your operating system.
Oracle provides drivers for:
Use a 64-bit driver with 64-bit Power BI Desktop. The driver and the reporting tool must use the same system type.
A 32-bit driver will not work with a 64-bit Power BI setup.
Create a role with the SuiteAnalytics Connect permission.
The role should include only the data needed for the report. Avoid giving broad access unless the project requires it.
For example, a sales dashboard may need:
It may not need payroll or employee data.
A smaller role is safer. It also makes the report easier to test.
Oracle supports OAuth 2.0 and token-based authentication for SuiteAnalytics Connect.
Oracle recommends OAuth 2.0 when possible. It offers a modern method for secure system access.
Token-based authentication also remains supported. It uses an integration record, user, role, and token details.
The setup steps differ for each method. Follow Oracle's current instructions for the method you select.
Do not share normal user passwords with reporting tools. Use a dedicated integration or reporting user.
Open ODBC Data Sources on your Windows computer.
Choose the 64-bit version when using 64-bit Power BI. Then open the System DSN tab.
Select Add and choose the NetSuite ODBC driver.
Enter the connection details shown in NetSuite:
The usual port is 1708. The data source should be NetSuite2.com.
Use the exact service host shown in your NetSuite account. Do not copy a hostname from another company or online guide.
Account settings can differ. The value from your own account is the safest choice.
Use the driver test option after entering the connection values.
A failed test often points to one of these problems:
Fix the connection before opening Power BI. This makes later troubleshooting much easier.
Open Power BI Desktop.
Select:
Get Data > ODBC
Choose the NetSuite DSN from the list. Enter any required authentication details.
Power BI may display available records in the Navigator window. You can also enter a SuiteQL query through the advanced options.
Start with a small query. Confirm the values before loading a large amount of data.
SuiteQL lets you control which NetSuite data Power BI loads.
A simple query may look like this:
SELECT
id,
tranid,
trandate,
entity,
foreigntotal
FROM
Transaction
WHERE
trandate \>= TO\_DATE('2024-01-01', 'YYYY-MM-DD')
This query selects five fields from the Transaction record. It also limits the results by date.
The date filter matters. Without it, the report may try to load years of old data.
Avoid using SELECT * in large reports. That command loads every available field.
Most dashboards need only a small part of each record. Selecting fewer fields can make the query faster and easier to maintain.
Useful filters may include:
Test each filter before building the full Power BI model.
Power BI normally uses Import mode with a standard NetSuite ODBC connection.
Import mode copies the selected data into the Power BI model. Users then view and filter the imported data.
The dashboard does not send a fresh query to NetSuite after every click. Instead, it shows the most recent imported data.
You can schedule refreshes through the Power BI Service. The refresh schedule depends on your Power BI plan and gateway setup.
DirectQuery is different. It sends queries to the source while users interact with the report.
A standard ODBC source does not always support DirectQuery. The connector must specifically support that mode.
Most NetSuite ODBC projects should plan around Import mode. A data warehouse may be a better choice when DirectQuery is required.
Report speed starts with the source query.
A slow SuiteQL query will create a slow refresh. Power BI cannot fully fix a weak source query.
Use these basic steps:
Do not use a fixed row count as the only guide. Oracle does not publish one row limit where all queries fail.
A query with many joins may run slowly with fewer rows. A simple query may handle a much larger result set.
The structure of the query matters more than one general row count.
Tableau can connect through an ODBC or JDBC driver.
The setup follows many of the same steps:
Tableau can create extracts from NetSuite data. An extract stores a copy of the selected data for faster reporting.
Extracts can reduce repeated queries against NetSuite. They can also support scheduled updates.
However, the source query still matters. A large and poorly filtered query may take a long time to build the extract.
Start with a limited date range. Add more data after confirming the report logic.
Excel can also connect through ODBC.
Open Excel and select:
Data > Get Data > From Other Sources > From ODBC
Choose the NetSuite DSN. Then select the required data or enter a query.
Excel works well for:
An Excel worksheet supports 1,048,576 rows. That does not mean you should load that much NetSuite data into one sheet.
Large files become hard to open and review. Power BI or a warehouse may work better for larger reporting needs.
Start with the simplest tool that meets the need.
A Saved Search may solve a basic reporting problem. There is no need to build a warehouse for a weekly invoice list.
Power BI becomes useful when users need several measures and visual reports. A warehouse becomes useful when many systems and reports share the same data.
Authentication is often the hardest part of the setup.
The driver must prove which NetSuite user and role it represents. NetSuite then applies that role's permissions.
Oracle recommends OAuth 2.0 when possible.
OAuth 2.0 can use different flows. The correct choice depends on whether a person signs in or a system connects on its own.
A machine connection may use the client credentials flow. This setup often includes:
Follow the Oracle OAuth 2.0 guide for current steps.
Token-based authentication uses an integration record and access token.
The setup often includes:
NetSuite only shows some values once. Store them in a secure password system.
SuiteAnalytics Connect may require a generated token password string. Do not assume the DSN accepts each token value in a separate field.
Use Oracle's current Connect instructions when building the authentication value.
The reporting role controls what the connection can read.
A role with broad access can expose data through Power BI or Tableau. The BI report may then share that data with more users.
Plan security in both systems.
In NetSuite, review:
In the BI tool, review:
A secure NetSuite role does not help if the Power BI report is shared with the wrong group.
The full data path must be secure.
Copy the Account ID from the SuiteAnalytics Connect setup page.
Sandbox accounts may use a different format from production accounts. Copy the full value exactly.
Check the assigned role.
The role needs SuiteAnalytics Connect access. It also needs permission for each record used in the query.
Confirm that the network allows outbound traffic on port 1708.
A company firewall may block the connection. Ask the network team to review the rule.
Make sure the driver was installed correctly.
Also confirm that the driver type matches Power BI. A 32-bit driver will not appear inside a 64-bit application.
Check the integration record, role, user, token, or OAuth setup.
Authentication values may expire or become invalid after account changes.
The reporting role may not have permission to view the record.
The record may also use a different NetSuite2.com name. Check the NetSuite Records Catalog for the correct record and field IDs.
SuiteQL does not support every SQL feature.
Check the record name, field name, function, and join. Test a smaller query to find the part causing the error.
The Oracle Connect documentation includes current setup and error details.
NetSuite stores related data across several records.
For example, a transaction may use:
The Transaction record holds header details. These may include the date, customer, and transaction number.
TransactionLine holds item and line details. TransactionAccountingLine holds accounting impact details.
The same report may need data from all three records.
Power BI may not find every relationship on its own. A report builder may need to define each link.
This is where many projects become difficult. The connection works, but the totals do not match NetSuite.
Review joins carefully. Compare the report against a known NetSuite total before publishing it.
The SuiteQL query guide can help teams learn the basic query process.
SuiteAnalytics Connect is a strong fit when:
It also works well for teams that want control over their queries.
The company should have someone who can maintain the connection. That person may be a NetSuite administrator, analyst, or data engineer.
Another setup may work better when:
A data warehouse may fit these needs.
The warehouse sits between NetSuite and the BI tool. It stores data from NetSuite and other systems.
Power BI then reads from the warehouse. It does not need to run every report directly against NetSuite.
Platforms such as Snowflake and BigQuery can serve this role. An integration tool can move the data on a schedule.
Celigo may support this type of pipeline. The right design depends on your systems and reporting needs.
Distributors often need a clear view of stock across several locations.
A Power BI report may combine:
Buyers can use this data to plan orders. Sales teams can also check product supply before making promises.
Anchor Group supports NetSuite for Wholesale Distributors. This includes inventory, purchasing, fulfillment, and vendor workflows.
Manufacturers may use BI tools to track work orders and material use.
Reports can show:
The report may combine production and accounting data. That gives leaders a clearer view of both output and cost.
The data model must match the company's manufacturing setup. Work orders, assemblies, routing, and WIP can change the report design.
Retailers often need sales and stock data from several channels.
A report may combine:
This helps teams compare demand across channels.
The report should also handle refunds and canceled orders correctly. Otherwise, sales may look higher than the final accounting total.
Software companies may use NetSuite data for subscription and revenue reports.
Common measures include:
These reports require clear accounting rules. The dashboard must match the company's billing and revenue setup.
A chart may look correct while using the wrong contract date. Always test the totals against approved finance reports.
Installing the driver is only one part of the project.
The harder work often comes later. Teams must choose the right records, joins, filters, roles, and refresh schedules.
Anchor Group helps companies build and improve NetSuite reporting systems through NetSuite Services.
Our team works with SuiteQL, integrations, roles, permissions, and NetSuite reporting. We also understand the business processes behind the records.
That matters because a working connection does not always produce a correct report.
The dashboard may count transaction lines twice. It may miss closed periods or use the wrong exchange rate. It may also show data that the viewer should not see.
Those problems need more than driver setup. They require careful report design and NetSuite knowledge.
For a specific problem, schedule a FREE 30-minute NetSuite fix. You can review the issue with an experienced consultant.
Companies that need ongoing support can use NetSuite Managed Services. Anchor Group can help maintain queries, connections, refreshes, and reports.
SuiteAnalytics Connect is NetSuite's official reporting connection service. It supports ODBC, JDBC, and ADO.NET drivers. Reporting tools use these drivers to run read-only SuiteQL queries. The service uses the NetSuite2.com data source. Access follows the assigned NetSuite role. It lets teams report on ERP data without changing records or building a custom API.
You can create a basic connection without writing software code. You must still install the driver and create a DSN. NetSuite permissions and authentication also need setup. Power BI can then browse records or load a SuiteQL query. Basic SQL skills help with filters and joins. A NetSuite administrator may need to complete the account steps.
Slow queries often load too many fields or records. Large joins can also increase the query time. Add date, subsidiary, status, or transaction filters. Select only the columns used by the report. Close connections that are no longer needed. Test each query before loading it into Power BI. A data warehouse may help with larger shared reports.
SuiteAnalytics Connect uses secure connections and NetSuite role permissions. The reporting user can only read data allowed by the assigned role. OAuth 2.0 is Oracle's preferred authentication choice. Token-based authentication also remains supported. Companies should protect stored credentials and review report sharing. Security must cover both NetSuite and the BI platform.
A warehouse may help when reports use several business systems. It also helps when many dashboards need the same large dataset. The warehouse stores a prepared copy of the data. Power BI or Tableau then reads that copy. This reduces repeated queries against NetSuite. A warehouse may also support DirectQuery, shared history, and stronger data controls.
Related Articles
