Skip to main content

​
General Troubleshooting

​
Performance Considerations

If you find NetSuite to be too slow, you can try the following to improve performance:
  • Limit selected columns

    NetSuite objects rely heavily on backend JOINs. Removing unused columns can eliminate entire JOINs and significantly improve performance.
  • Reduce page size

    Lowering the Pagesize property returns fewer records per request and can help avoid timeouts before all the results are returned. This property is found in Edit NetSuite Connection > Advanced Settings.

  • Caching

    You should also consider using the Connect AI Caching feature for better performance.

​
Schema Support and Performance

In general, performance is best in SuiteAnalytics. Connect AI exposes CData’s NetSuite driver as well as NetSuite’s native SuiteAnalytics driver as separate connectors. We recommend using the native SuiteAnalytics driver, if your organization has access to it, for best performance. If you do not have access to SuiteAnalytics, use the CData’s NetSuite driver.

​
Manage Integrations Visibility

To see Setup > Integrations > Manage Integrations in NetSuite, the role must have both of these permissions:
  • Integration Application (Full) under Setup.
  • Integration Applications (Full) under Lists.
See Permissions Configurations for more information.

​
Common Errors

​
SuiteQL Errors

This issue is usually a permissions issue to access the object type when using the SuiteQL schema. Note that permissions could apply to either the table or any of the columns in the table. The driver attempts to do a RowScan to determine which fields are available.Check your NetSuite role to see if the table is included:
  1. Log in to your NetSuite account as an administrator.
  2. Navigate to Setup > Users/Roles > Manage Roles.
  3. Select the role you are using to connect with the driver.
  4. Click Edit > Permissions.
  5. Under Setup, add Full permissions for the table you need.
View the complete list of permissions required by our driver here.In some cases, the table may have been deprecated or removed by NetSuite. Check whether another table exposes the same data.
  • If Connect AI cannot find a column, it may be due to cached or outdated metadata. Clear the metadata cache, if applicable, by clicking Clear Metadata on the Edit NetSuite Connection page.
  • It is also possible that the RowScanDepth property is zero. In that case, increase the Row Scan Depth property in the Advanced Settings tab of the Edit NetSuite Connection page to a non-zero value.
The SuiteQL schema can only return a maximum of 100,000 records. This limitation is imposed by NetSuite itself. You can bypass this limitation in one of two ways:
  • Set your Schema to SuiteTalk rather than Suite QL.
  • Use the SuiteAnalytics Connect feature. If your account has SuiteAnalytics Connect, enable the SuiteAnalytics Connect feature by setting the AccountSupportsSuiteAnalyticsConnect property to True.
If you receive this error, you have not set the required Custom Fields permissions in NetSuite. See Permissions Configurations.

​
SuiteTalk Errors

Adjust the permissions for custom records. See Permission Configurations.
This error appears when the role that you select during OAuth login is not configured for OAuth. If you have an OAuth-configured role, click Choose another role on the NetSuite authorization page and select that role. If you do not have an OAuth-configured role, follow the steps in the Configure Roles section.