Saved search to code, in one click
I use this every day. You build the search in the UI because it is fast, then you would normally spend an hour retyping it into SuiteScript, field by field, hoping you do not fat-finger a field ID. This generates the code instead: copy, paste, ship. It is free on the Chrome Web Store. Install it.
- Not an hour of retyping
- Seconds
- Field-ID typos
- Zero
- On the Chrome Web Store
- Free
Transcribing searches is not the work
The drill was always the same: build the search in the UI, test it, then need it in code. So I would start typing. Record type, filters (hope I remember the operator syntax), columns (hope I spell the field IDs right), formulas (escape all the quotes), maybe a join or two, then debug the typos and test again. Thirty to sixty minutes for something that already existed.
The search was already defined. The code should just fall out of it. So I built the thing that does that, and got those hours back for the parts that actually require thinking.
It exports everything
SuiteScript 1.0 & 2.X
Export to nlapiSearchRecord or the modern N/search module. Legacy or current, your choice.
Console-ready code
Test the search immediately in browser DevTools. No deployment, no waiting.
SuiteQL for datasets
Export datasets and workbooks as clean, formatted SuiteQL queries.
No data leaves your machine
Everything runs in your browser. Your search definitions never go anywhere.
Three steps, no setup
Open → Export → PasteOpen your saved search
Navigate to any saved search in NetSuite, in edit mode.
Click Export as Script
Pick the format: SS 1.0, SS 2.X, Console, or Text.
Copy, paste, ship
One-click copy, paste into your script, and move on.
The moments it earns its place
I built the search in the UI and now need it in code
The fast way to define a search is the UI. Retyping it into SuiteScript by hand is the slow, typo-prone part. This skips straight to the generated code.
I want to test a search in the console first
Console-ready output lets me paste into DevTools and confirm the search returns what I expect before it ever lands in a script file.
I am pulling a dataset or workbook into SuiteQL
When the source is a dataset, I export it as clean SuiteQL instead of reverse-engineering the query by hand.
For the people who care how it is built
- Chrome Manifest v3, the current extension architecture
- SuiteScript 1.0, nlapiSearchRecord() format
- SuiteScript 2.X, the modern N/search module
- SuiteQL for datasets and workbooks
- XSS protected, CSP hardened
- WCAG accessible, keyboard nav and screen-reader support
- Record type and search ID
- All filters with operators and values
- All columns with labels (optional)
- Join fields with correct syntax
- Formula fields, properly escaped
- Sort orders and directions
- Summary types (GROUP, SUM, COUNT, etc.)
- Filter expressions for complex logic
- Console-ready code for instant testing
- Human-readable text for documentation
Output is clean, formatted code ready for your SuiteScript files.
Zero data collection
No analytics, no telemetry, no tracking. The extension does not phone home.
100% local processing
Everything runs in your browser. Your saved-search definitions never leave your machine.
Minimal permissions
It only touches NetSuite saved-search pages. Nothing else.
Inspect it yourself
The code is not obfuscated. Open Chrome's extension viewer and read exactly what runs.
Try it on one saved search
It is free. Install it, export one saved search, and see the code for yourself. The next search you need in code will take seconds, not an hour.