Accessing the Connect Service Using Microsoft Excel

You can use the SuiteAnalytics Connect ODBC driver to load your NetSuite data to Microsoft Excel workbooks.

Before you can configure Microsoft Excel to pull data from the SuiteAnalytics Connect data source, you need to download and install the latest SuiteAnalytics Connect ODBC driver and make sure it is connected to your NetSuite data source.

Important: The following instruction is based on a 32-bit SuiteAnalytics Connect ODBC driver used in conjunction with 32-bit Microsoft Excel 2016. Please note that the examples in this instruction are provided for illustrative purposes only. The tables available in your NetSuite account may vary.

To load data using a query:

1. In Microsoft Excel, go to the Data tab and select New Query>From Other Sources>From ODBC.

   1. • 

2. In the connection string field, typeDSN=NetSuite; to use the Connect driver DSN for connection.
3. Expand the SQL Statement area and enter your SQL query. For example, to run a query over all columns in the Service Items table, enter select * from service_items; If you don’t add any query in the SQL Statement field, you can click OK and select a table or a set of tables you want to open in the Query Editor. However, there can be Excel limitations to using this option. In this case, try running the query again, adding an explicit query statement in the SQL Statement field.

4. Click OK.

5. Provide your NetSuite login and password, if prompted, and click Connect.

6. The Query Editor opens. You can rearrange the columns in your query, removing those you do not need.
7. When ready, click Close & Load to load your query data to your Excel workbook. By default, your data will be loaded to a new worksheet. For more options, expand this menu and click Close & Load To.

Note: Due to an Oracle limitation, queries over SuiteAnalytics Connect schema tables including more than 999 fields will not run. This may happen when querying over tables that have many custom fields or when joining multiple tables in a single query and trying to retrieve all their fields. For example, if you add too many custom fields to the Transaction record type, exceeding the 999 fields per table limit, you may get the following error: “Error: Could not find any column information for table:transactions”.