Third-Party Application Access
If you're having trouble accessing SuiteAnalytics Connect, check these potential issues and make any necessary adjustments.
-
During the development stages of working with the SuiteAnalytics Connect for ODBC driver, you can use Windows administrative tools to set up ODBC access to work with your NetSuite Sandbox or Release Preview account instead of your production account. For more information, see Driver Access for a Sandbox or Release Preview Account.
-
You should not use IP addresses to access the Connect Service in your firewall configurations. For more information, see Prerequisites for Using the Connect Service.
-
Logins to SuiteAnalytics Connect are tracked in the Login Audit Trail. For more information, see Using the Login Audit Trail.
-
The order in which column values are returned is arbitrary. NetSuite doesn't guarantee the return order. In addition, Microsoft Access supports only 255 columns per result set. If you use Access to get results from the Connect Service that include more than 255 columns, it's not possible to see all of the table’s column values in a single result set.
-
Queries over SuiteAnalytics Connect schema tables that have more than 1000 columns only work if you retrieve 1000 columns or less in the query. Using “Select * From” with tables that have many custom fields or joining multiple tables can cause errors. For more information, see Custom Field Limitations.
-
SuiteAnalytics Connect requires TLS-secured connections. If you use a JDBC driver to access SuiteAnalytics Connect and you've specified a cipher suite in your connection URL, you should remove the cipher suite from the URL. If the connection URL doesn't include a cipher suite, the JDBC server automatically selects the appropriate cipher suite for authentication. If you use an ODBC or ADO.NET driver to access the Connect Service, no action is required. For more information, see Authentication Using Server Certificates for JDBC and Supported TLS Protocol and Cipher Suites.