NetSuite Field Explorer vs MokuBot: Two Different Questions
If you work in NetSuite and have ever needed a field's internal ID, you have probably installed NetSuite Field Explorer. Around 40,000 people have. It is one of the most widely installed NetSuite tools that Oracle did not write, and it earned that position.
We build a different NetSuite Chrome extension, so treat what follows accordingly. We have tried to write the comparison we would want to read, which means being specific about where Field Explorer is the right answer and we are not.
The short version: they answer different questions. Field Explorer answers what is this field called. MokuBot answers do the thing that field is part of. If your work is mostly the first question, the free tool is the correct choice and this page can end here.
What Field Explorer actually solves
The native way to see field IDs on a record is to append &xml=T to the URL. NetSuite returns the record as XML and you read the tags.
It half works. The XML reflects the form, not the record. Fields hidden by the current form, restricted by your role, or simply not placed on the layout are absent. You go looking for a field, do not find it, and conclude it does not exist. It does. You were looking at a filtered view and nothing told you it was filtered.
Field Explorer reads the record rather than the rendered form. It puts the fields in a collapsible tree next to the record, gives you a search box, and lets you copy an ID with one click. That is the entire product, and the reason it has 40,000 users is that it does that one thing without friction: no login, no configuration, no account connection, no waiting. Install it, open a record, the panel is there.
There is a small ecosystem around it now, which is worth knowing about because the original has not shipped an update in a while:
- Field Explorer Plus adds expand/collapse all, copy-as-JSON, direct links into the Records Browser and Records Catalog, and is built on Manifest V3.
- NS Next Field Explorer targets the newer NetSuite Next interface, where the original does not attach.
- NetSuite Record Explorer rebuilds the idea for Manifest V3 and copies whole records as Full, Schema, or JSON output. Its listing says the JSON mode is there so you can paste the record into an AI chat.
That last one is a good signal about where this category is drifting, and we will come back to it.
Where the two tools actually differ
| Field Explorer | MokuBot | |
|---|---|---|
| Primary job | Inspect the current record's fields | Query, build and change things in your account |
| Scope | The record you have open | The account: searches, SuiteQL, records, scripts, logs |
| Output | Field names and values you copy | A saved search, a query result, a script, an executed action |
| Input | You navigate to the record | You describe what you want |
| Writes | Never. Read-only by design | Read-only by default; writes are per-permission and explicit |
| Setup | Install and go | Install, connect the session, configure permissions |
| Cost | Free | Code editor and Dependency Audit free; the AI agent is paid |
| Works offline from your account | Yes | No |
The row that matters is the first one. Field Explorer is an inspector. Inspectors are excellent when the bottleneck is knowing. They do nothing for you when the bottleneck is doing.
Concretely: you need every sales order over $10,000 from last quarter that shipped late, grouped by sales rep. Field Explorer will happily tell you that the ship date field is shipdate and the custom SLA flag is custbody_sla_breach. It will not tell you that you need Main Line = true so the amounts do not double, that the rep join is salesrep.entityid, or that "shipped late" has to be a formula because there is no field for it. Those are the parts that take the twenty minutes. The field name took ten seconds, and Field Explorer made it take two.
That is not a criticism. It is a statement of scope, and it is why we think a lot of people should keep using both.
What MokuBot does instead
MokuBot is an agent that runs in a side panel inside your authenticated NetSuite session. You describe what you want in plain language and it operates against your actual account: building and running saved searches, writing and executing SuiteQL, reading and editing records, generating SuiteScript, and reading script logs to explain why a deployment is failing.
The relevant difference for this comparison is that field IDs stop being a step. When it builds a search it resolves fields against your account, so your custom fields are simply present, with the custbody / custcol distinction handled rather than explained to you. The knowledge Field Explorer surfaces for you to carry to the next step is consumed internally instead.
The failure modes are different too, and worth stating plainly. An inspector cannot be wrong: it shows you what is there. An agent can be confidently wrong. That is why MokuBot is read-only unless you grant write permissions, why writes are granular, and why you should read a generated search before saving it, the same way you would read a pull request. If you are not going to review the output, use the inspector.
When Field Explorer is the better tool
We would rather say this than have you discover it after paying us.
When you only need the field name. A single ID, once, to paste into a script you are already writing. Field Explorer wins on latency and always will. There is no version of an agent that beats a panel that is already open.
When you cannot connect anything to the account. Locked-down role, client environment, security review pending, air-gapped policy. Field Explorer is a local viewer over a page you already have permission to see. That is a much easier conversation with a security team, and sometimes it is the only conversation that ends in yes.
When budget is genuinely zero. Free is a real feature. If you are one admin in a company that is not going to approve a tool spend, install Field Explorer and use the SuiteQL query tool that ships with NetSuite. That combination gets you a long way. For completeness, our code editor and its dependency mapping are also free and unmetered, so a zero-budget setup can include all three; the agent is the part that costs money.
When you are learning the schema. Clicking through a record tree and seeing how NetSuite structures things builds a model in your head that having answers handed to you does not. If you are six months into NetSuite, the slow way is an investment.
When the inspector stops being enough
The pattern we see is that people outgrow the inspector rather than dislike it. The tell is what happens after you copy the field name.
If the answer is "I paste it into a script or a search and move on", you have a lookup problem and a lookup tool solves it.
If the answer is "I copy the field name, then figure out the join, then get main line wrong, then check the Records Catalog, then rebuild the search because grouping needs a Summary criterion", you have a construction problem and the lookup was a small part of it. We wrote up that whole surface separately in what actually breaks in saved search formulas, and the honest summary is that field IDs are maybe ten percent of it.
The Record Explorer extension we mentioned earlier is interesting precisely because its author noticed this. Copying a whole record as JSON so you can paste it into an AI chat is people routing around the gap by hand: inspect, serialise, paste into a model, get an answer, come back and apply it. It works. It is also four steps and a context switch, with a copy of your record data pasted into whatever chat window happened to be open.
MokuBot is the same idea with the loop closed, running inside the session that already has the data, under permissions you set. That is the argument. Whether the difference is worth paying for depends entirely on how many times a week you run that loop.
Using both
There is no conflict. They are separate extensions, they do not fight over the page, and they are good at different moments. Plenty of our users have Field Explorer installed, and if they asked, we would tell them to keep it.
Our actual recommendation, without much regard for which one you pay for:
Install Field Explorer today. It is free, it takes thirty seconds, and it fixes a real gap in NetSuite that Oracle has never closed. If your day is mostly reading records and looking things up, you are done and you owe nobody anything.
If your day is mostly building things (searches that have to be right, scripts that have to deploy, data that has to be corrected across a few hundred records), the inspector is solving the easy ten percent. That is where it makes sense to look at what MokuBot does and decide whether the other ninety is worth a subscription to you.
We would rather you install the free thing and never come back than pay us for a problem you do not have.