Key Takeaways
- NetSuite’s native UI does not surface field IDs inline: Extensions like Show Field IDs and Field Explorer fill this gap, eliminating the need to dig through documentation or the Records Browser during active development.
- Script deployment visibility is a recurring pain point: NetSuite Scripted Records solves it by showing all scripts on a record in one panel and allows you to undeploy or redeploy without navigating through Setup.
- Transaction relationships are not natively visible on the transaction form: Transaction Tree surfaces the full parent-child chain in a single popup, with bulk delete available for test or cleanup scenarios.
- Extracting SuiteScript code from a saved search normally requires manual reconstruction: Search Export generates the equivalent N/search code directly, cutting the time to reuse an existing search in a script from minutes to seconds.
- These five extensions are focused on development and administration workflows: For a broader list covering business users and reporting tools, see the 25+ NetSuite extensions roundup on this site.
Introduction
SuiteScript development and NetSuite administration involve a recurring set of small tasks that the native interface handles slowly or not at all. Finding a field ID means hovering through help text or navigating to the Records Browser. Knowing which scripts run on a record means checking Script Deployments in Setup. Understanding a transaction’s related records means opening each one manually.
Chrome extensions address these gaps directly. They run in the browser alongside NetSuite and inject additional UI elements, panels, and tools that surface information the native interface hides. The five extensions below are ones that developers and administrators use regularly in active development.
1. NetSuite Record JSON Viewer
What It Does
Converts the current NetSuite record into a JSON representation and displays it in a readable format. One click on the extension icon outputs the full record structure: field IDs, current values, sublist data, and record metadata.
Who It Is For
Developers debug field values during script development. Administrators verify what data is on a record without opening each field individually. Anyone who needs to compare the record state before and after a process runs.
Why It Matters
NetSuite’s standard record view shows labels, not field IDs or raw values. When a script behaves unexpectedly, the first question is usually ‘what is the actual value of this field right now?’ JSON Viewer answers that immediately, without writing a console log or loading the record in a separate script context.
- Shows all body fields and their current values
- Includes sublist data
- Displays record type and internal ID
- Output is copyable for sharing or debugging logs
2. NetSuite Scripted Records
What It Does
Displays all scripts deployed to the currently viewed record in a single panel. For each deployed script, it shows the script name, script type, deployment status, and the events it fires on (beforeLoad, afterSubmit, etc.). It also allows you to undeploy or redeploy scripts directly from the panel.
Who It Is For
Developers troubleshooting unexpected behavior on a record by confirming which scripts run on a record, which required navigating to Customization > Scripting > Scripts and filtering. Administrators auditing which customizations affect specific records. Anyone onboarding to an existing NetSuite account with customizations they did not build.
Why It Matters
NetSuite accounts built up over years accumulate scripts across many record types. When a record behaves unexpectedly, identifying whether a script is causing it is the critical first debugging step. Without Scripted Records, that means a Setup navigation, a search, and cross-referencing deployment records. With it, the answer is one click.
- Lists all scripts deployed to the current record
- Shows script type: Client Script, User Event, Workflow Action, etc.
- Displays deployment status: Testing, Released, or Inactive
- Undeploy and redeploy scripts without leaving the record
For a broader overview of how script types interact with records and when each fires, the SuiteScript essentials getting started guide covers User Event Scripts, Client Scripts, and other types with deployment context.
3. NetSuite: Show Field IDs
What It Does
Displays the internal field ID of any field on a NetSuite form when you hover over it. Also provides a keyboard shortcut (Ctrl+Shift+F / Cmd+Shift+F on Mac) to search for any field on the current record by its ID.
Who It Is For
Developers writing SuiteScript who need field IDs for getValue(), setValue(), getField(), and search column references. Administrators creating saved searches, workflows, or custom fields that reference existing field IDs. Anyone building an integration that maps NetSuite fields to external system fields.
Why It Matters
Field IDs are not displayed in NetSuite’s standard form UI. The native method shows the ID buried in help text, one field at a time. Show Field IDs surfaces the ID directly next to the field label, permanently visible while the extension is active. The search shortcut makes it faster to confirm a field exists on a record before referencing it in code.
- Field ID visible on hover, no clicks required
- Works on standard and custom fields
- Works on body fields and sublist fields
- Keyboard shortcut to search field by ID on the current record
Custom fields follow a naming convention (custbody_, custentity_, custitem_, etc.) that predicts their IDs, but standard field IDs are not always obvious from the label. For more on how custom fields are created and named, see our guide to adding custom fields to NetSuite items.
4. NetSuite Transaction Tree
What It Does
Adds a ‘Transaction Tree’ link to all eligible transaction records. Clicking it opens a pop-up showing every parent and child transaction linked to the current one — the full transaction chain from source document to final posting. Each related transaction has a checkbox, and selected transactions can be opened or deleted in bulk.
Who It Is For
Developers testing transaction workflows who need to clean up test data — including all linked fulfillments, invoices, and payments — without opening and deleting each record individually. Administrators investigating a transaction issue who need to trace the full chain: original sales order, fulfillments, invoices, deposits, and payments. Consultants reviewing how a client’s transactions relate to each other.
Why It Matters
NetSuite displays related transactions in the Related Records subtab, but it shows a flat list without the hierarchy. Transaction Tree shows the parent-child structure visually, making it clear which record created which. The bulk delete is particularly useful in development and sandbox environments where test transactions accumulate and need cleanup without navigating through each one.
- Shows full parent-child transaction hierarchy in a popup
- Each related transaction is clickable to open directly
- Checkbox selection enables bulk open or bulk delete
- Works on any eligible transaction: Sales Orders, Invoices, Fulfillments, Payments, POs
5. NetSuite: Search Export
What It Does
Extracts the SuiteScript code equivalent of any saved search in NetSuite. After installing and navigating to a saved search, clicking the extension generates N/search module code that recreates the search programmatically: search type, filters, columns, and sort order.
Who It Is For
Developers who need to run an existing saved search inside a script. Rather than manually reconstructing the N/search.create() call by reading the saved search configuration and translating each filter and column to code, Search Export generates the code directly. Administrators who want to understand what a saved search is actually doing at the field level.
Why It Matters
Translating a saved search to SuiteScript manually is one of the most repetitive tasks in NetSuite development. A saved search with 8 filters and 12 columns takes meaningful time to transcribe accurately, including getting the join syntax, operator names, and column IDs correct. Search Export eliminates that transcription step entirely.
- Generates N/search.create() code from any existing saved search
- Includes search type, all filters with operators and values, all result columns
- Output is ready to paste into a SuiteScript file
- Works with saved searches of any record type
For a walkthrough of how N/search works in practice — including how search results are iterated and exported to CSV, see the guide to creating CSV files from saved search results in SuiteScript.
Installation and Compatibility
All five extensions install from the Chrome Web Store. They work in any Chromium-based browser: Chrome, Edge, Brave, and Arc. None require NetSuite administrator access to install, they run in the browser and read the DOM of the currently loaded NetSuite page.
They are compatible with NetSuite’s SuiteScript 2.x environment and work with current NetSuite releases. As NetSuite updates its UI (particularly during the twice-yearly version releases), extension compatibility occasionally lags by a few weeks until the extension developer pushes an update. If an extension stops working after a NetSuite release, check the Chrome Web Store listing for a pending update.
Choosing the Right Extension for the Task
- Debugging unexpected field values on a record: JSON Viewer — outputs the full record state in one click
- Identifying which scripts are running on a record: Scripted Records — lists deployments with script type and status
- Finding field IDs during scripting or workflow setup: Show Field IDs — surfaces IDs inline on the form
- Understanding a transaction’s related document chain: Transaction Tree — shows parent-child hierarchy with bulk actions
- Reusing a saved search in a SuiteScript: Search Export — generates the equivalent N/search code directly
These five cover the most common developer and administrator friction points. For a more extensive list covering business users, reporting tools, and non-developer extensions, see the full 25+ NetSuite Chrome extensions guide which includes extensions for dashboards, exports, and field metadata visualization tools like NetSuite Field Explorer.
Conclusion
These five extensions do not change what NetSuite does. They change how fast you can see what is happening inside it. JSON Viewer, Scripted Records, Show Field IDs, Transaction Tree, and Search Export each address a specific moment in the development or administration workflow where the native interface creates unnecessary friction.
Install all five. Use them as defaults. The time saved across a single sprint of development work makes the installation cost negligible.
The right tools can eliminate hours of repetitive investigation, troubleshooting, and navigation inside NetSuite. If you’re looking to improve developer productivity, streamline administration, or optimize your NetSuite environment, book a meeting with our NetSuite experts. We’ll help you identify practical enhancements, best practices, and custom solutions that enable your team to work more efficiently.
