Skip to content

Settings

The Settings page controls how NimbusQL runs queries and how long the records catalog is cached. These settings apply to every user in the account.

Settings currently includes two options: Query method and Schema cache. Only the values listed on this page can be saved.

  1. Open NimbusQL in NetSuite
  2. Click Settings in the left navigation

This page is available to NetSuite Administrators and other users with full NimbusQL access. Other users see a message that this feature can only be used by NetSuite Administrators.

After you change a value, click Save Settings. A confirmation appears when the save succeeds.

Query method chooses how NimbusQL executes SuiteQL for everyone in the account.

  • runSuiteQL — the default. Fastest. Column names can be inconsistent when a result set has more than 5,000 rows.
  • runSuiteQLPaged — slower. Column names stay consistent.

Use runSuiteQL unless you need stable column names on large result sets.

Schema cache controls how long NimbusQL keeps the records catalog before autocomplete and Schema Explorer rebuild it.

A longer lifetime means new custom records and fields take longer to appear. A shorter lifetime means more rebuilds. A rebuild reads every record type in the account and can take several minutes.

Allowed values:

  • 1 day
  • 3 days
  • 7 days (default)
  • 14 days
  • 30 days
  • Never (rebuild on every page load)

Never rebuilds the catalog on every Write Query page load. Use it only for debugging or when the schema is changing rapidly. That cost applies account-wide, including to users who only run Reports.

To rebuild once without changing this setting, open Write Query, click Schema, and click Rebuild schema cache.

  • Both settings are account-wide. Saving them affects every NimbusQL user.
  • Schema Explorer and autocomplete share the cached catalog. Changing Schema cache or using Rebuild schema cache updates both.