Analyzer

Shipped

The Customization Analyzer, at /admin/analyzer in your Turbobase app (administrators only, with its own main-navigation entry), maps what your connected Oracle NetSuite account has actually been customized into (the custom fields, records, lists, and scripts accumulated over years) and turns that inventory into something you can reason about: what exists, what’s actually used, and what carries risk. Findings flow into the Development pipeline as signals and proposals rather than staying a static report.

The Analyzer is NetSuite-specific today. Its pages render from the last collected snapshot — opening them issues no new calls against your account — so until the first collection runs you’ll see an empty state with the collection progress and any per-step failures called out.

Tabs

• Overview — the landing view: headline counts across the collected inventory plus a summary of the latest usage analysis.

• Catalog — the unified customization catalog: every collected object — fields, records, lists, scripts, workflows, roles, custom forms, and saved searches — in one list, joined to any open risk findings. Every object opens a drawer with a plain-English explanation of what it does; scripts additionally show the pulled source and candidates for replacing them with native Turbobase capability, and where a release carries git provenance the drawer links to the source on GitHub. Bundle membership can’t be collected automatically — the page flags when it is missing, so Turbobase can run that collection against your account.

  The shared helper files your scripts load are listed here too, under the same Scripts filter with a script type of LIBRARY — most real scripts keep a meaningful part of their logic in shared files, and until they are listed that logic is invisible. A script’s drawer names the helpers it loads, a helper’s drawer names the scripts that load it, and each entry opens the other object; a helper also links out to its file in the NetSuite file cabinet. A helper file has no generated explanation and no source of its own on the Catalog, and it can’t be added to a managed release — it is there to be read and navigated. An import that resolves to no file in your account is kept as written rather than dropped, so nothing is quietly lost from a script’s dependency list.

  A script’s drawer also carries what your account’s own script record says, without anyone signing in to read it: the API version, the description whoever wrote the script left on it, and whether the record itself is switched off — which is a separate fact from whether a deployment is active, since a switched-off script can still hold a deployment that reads as deployed. A field your account never filled in shows no row at all, rather than an empty one.

• Usage — per-field usage analysis derived from the NetSuite audit trail, so you can see which customizations are actually exercised and which are dead weight. Run a scan from here; the tab also surfaces read-only hook candidates the analysis suggests, each deep-linked into Development. The old field-usage dashboard under /data/learning permanently redirects to this tab.

• Features — which NetSuite features are enabled on the account, with usage intensity.

• Instrumentation — runtime telemetry for the scripts Turbobase manages on the account.

What risk analysis covers

Collected scripts are classified by origin — uploaded to the account versus installed by a partner bundle — and risk detection flags exposures in them as findings on the Catalog. By default only account-uploaded script source is read.

Findings are grouped into five risk families so you can triage by the kind of exposure: inventory, GL posting, fulfillment, data integrity, and security.

An admin setting, “Read partner/bundle source for risk analysis”, extends reading to partner/bundle-owned script source so the risk detector can flag exposures there too. It is read-only by design and off by default: enabling it never makes a partner script manageable — partner source is tagged risk-only and can never enter the managed-bundle, proposal, or write-back path.

Related

• Development — where Analyzer findings become proposals and releases
• Custom fields — promoting discovered custom fields into queryable columns