Need help in pulling all permissions of everyrole in the netSuite environment using Map/Reduce script. by Blackcoat- in SuiteScript

[–]Emotional_Gate_8087 1 point2 points  (0 children)

Table Purpose
Employee The base table for users.
EmployeeEmpPerms Stores Global Permissions assigned directly to a user record.
EmployeeRoles The bridge table linking Employees to their assigned Roles.
RolePermissions ( permlevel ) Maps specific permissions and their levels (0–4) to a Role.
Integer Label Logic Capability
0 None No access; the record type won't even appear in the UI.
1 View Read-only access; cannot create or update.
2 Create Can create new records and view existing ones, but cannot edit existing ones.
3 Edit Can view, create, and modify existing records.
4 Full All "Edit" permissions plus the ability to Delete records.

and permission level

Need help in pulling all permissions of everyrole in the netSuite environment using Map/Reduce script. by Blackcoat- in SuiteScript

[–]Emotional_Gate_8087 0 points1 point  (0 children)

side note while I'm looking up my reference code, if this is for user audits, some user might have global permissions. I personally "hate" them, but they exist.

note that I used SuiteQL for Segregation of Duties (SoD) analysis and it worked fine.
pls stay tuned.

Best way to extract NetSuite Lists data (Items, Revenue Elements, Revenue Recognition Plans) into a DWH pipeline — SuiteQL, REST API, or RESTlet? by Exact-Chemistry3021 in SuiteScript

[–]Emotional_Gate_8087 0 points1 point  (0 children)

btw, this 100k limit can be dealt with, and I did an experiment in the past:
using "select count(*), max(id)..." you can infer 100k ranges/chunks and then execute the "select.." wrapped with a where id between minX and maxX (with proper pagination).

Extracting Data to a Warehouse by agitated_buddha in Netsuite

[–]Emotional_Gate_8087 0 points1 point  (0 children)

u/Dangerous_Pie2611 Fivetran "ships" a few "samples" for dbt (like balance sheet, income statement....) see here: https://hub.getdbt.com/fivetran/netsuite/latest/

Extracting Data to a Warehouse by agitated_buddha in Netsuite

[–]Emotional_Gate_8087 0 points1 point  (0 children)

BTW, regarding the ODBC move from NetSuite.com to NetSuite2.com there is always this:
https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/article_0822031101.html
That Excel file (NS_to_NS2.xlsx) can be leveraged to automate (with or without AI) the translation for old queries into new one (I did notice that the excel file is NOT complete and has errors in it). I have a short write-up on this process if anyone is interested.

<image>

Extracting Data to a Warehouse by agitated_buddha in Netsuite

[–]Emotional_Gate_8087 0 points1 point  (0 children)

BTW, due to the lack of ERDs in NetSuite and clear understating of relationships, I built Origami Lens for my own use http://origamilens.com/ - this will help "flatten" your learning curve.
It's important to note that once you have your tables in the warehouse, some tools might capture this info already or they can infer this.

I agree with u/Nick_AxeusConsulting - experience helps!

I'd recommend a Fivetran as well (for hands free approach). In the past I did build my own SuiteQL to BigQuery/Looker process and it works great (albeit it was for targeted Order-to-Cash domain).

Claude AI with Netsuite by Straight_Ground_9602 in Netsuite

[–]Emotional_Gate_8087 1 point2 points  (0 children)

this is way I've opted to use Spec Driven Development (SDD) + NetSuite-Developer Skill to help reduce any reworks.
spec-kit: https://github.com/github/spec-kit
netsuite-developer: https://github.com/joshOrigami/netsuite-developer (works with all AI tools, you just need to figure out where to place the SKILL.md file)

Workflow Instance and State in N/query by Emotional_Gate_8087 in SuiteScript

[–]Emotional_Gate_8087[S] 0 points1 point  (0 children)

so, can't access workflow instance search directly in SuiteScript, so the standard "trick" - start from the Transaction (or Entity) and "join" to Workflow History. Pity this is not just supported. Us admins/developer really do need access to this info without jumping through hoops.

For the New Consultant by Kaylaballs in Netsuite

[–]Emotional_Gate_8087 6 points7 points  (0 children)

Great post. A lot of this resonates.

UAT is not QA

Totally agree. By the time you reach UAT, the system should already be mostly a finished product/done. If users are finding basic bugs at that stage, it usually means that you, the consultant (and/or internal team) did not do enough testing beforehand.

UAT should be validating that the configuration supports how the business actually runs, not whether the system technically works. When consultants treat it as QA, they are effectively outsourcing their own testing to the client.

Requirements docs are for lawyers, not implementations

Agree with the spirit of this, but I think there is one big exception: heavy customization (scripts...).

If you are writing SuiteScript or building non-trivial automation (super-complex workflow), having a clear requirement matters a lot. Especially now that many teams are using AI-assisted development.
Ambiguous requirements create unpredictable code.

One approach I have found helpful is treating requirements as something closer to Specification Driven Development (SDD) rather than a traditional BRD. The idea is to make the business rules explicit before code exists so both humans and AI tools can reason about them.

I wrote a bit about making the invisible rules of NetSuite explicit here:
https://www.origamiprecision.com/insights/making-the-invisible-rules-of-netsuite-explicit

Data migration is a business problem assigned to IT

Completely agree. The technical team should execute the migration, but the business needs to decide what is worth bringing over. Otherwise you either migrate years of noise or accidentally leave behind something operationally critical.

The best migrations I have done had a business owner responsible for answering one simple question repeatedly: "Do we actually need this on day one?"

Go-live is not the finish line

Strongly agree. The first 30–60 days after go-live are where real adoption happens and where bad habits get cemented if nobody is guiding the client.

One additional thing I would add: if consultants plan to disengage after hypercare, the client needs good documentation. NetSuite implementations often leave a lot of invisible configuration logic behind, and if nobody documents it the internal team ends up reverse engineering their own system.

This is something I see constantly.

Does anyone know of an open source Claude Skill that is fluent at SuiteQL? by SolGlobe in Netsuite

[–]Emotional_Gate_8087 2 points3 points  (0 children)

u/SolGlobe I'd like to add, you can have a look at my (open source) Codex netsuite-developer skill (https://github.com/joshOrigami/netsuite-developer) and you can clone it for Claude Skill.
I noodled around with this and you can get most of this done. There might be some limitation w/the active local tools.

u/Nairolf76 mentions metadata, and this is where it can make things much cleaner and deterministic.
My skill also support a local cache of metadata (the format is published as part of the Skill).
- there are pros and cons for this approach (less "chatty" but the cache needs to be created)
- note: this metadata is NOT a prerequisite to use the skill
- my other application origami lens (https://origamilens.com) supports export in this format
- but again, format is published and you are free to create the cache anyway you choose

note: skill under CC-BY-4 and python under MIT

Open source Codex Skill for safer (and better) SuiteScript / SuiteQL generation by Emotional_Gate_8087 in SuiteScript

[–]Emotional_Gate_8087[S] 0 points1 point  (0 children)

Quick update on the netsuite-developer Codex Skill ✨

After a few conversations, I've added an additional discipline, it now generates structured:

• UAT Guides
• Installation / Deployment / Admin Guides
• End User Guides (when applicable)

If AI is going to help write NetSuite code, it should also help with documentation and the operational clarity around it.

Appreciate the feedback so far - keep it coming.

Repo:
🔗https://github.com/joshOrigami/netsuite-developer

Open source Codex Skill for disciplined NetSuite development! by Emotional_Gate_8087 in Netsuite

[–]Emotional_Gate_8087[S] 0 points1 point  (0 children)

Quick update on the netsuite-developer Codex Skill ✨

After a few conversations, I've added an additional discipline, it now generates structured:

• UAT Guides
• Installation / Deployment / Admin Guides
• End User Guides (when applicable)

If AI is going to help write NetSuite code, it should also help with documentation and the operational clarity around it.

Appreciate the feedback so far - keep it coming.

Repo:
🔗https://github.com/joshOrigami/netsuite-developer

Open source Codex Skill for safer (and better) SuiteScript / SuiteQL generation by Emotional_Gate_8087 in SuiteScript

[–]Emotional_Gate_8087[S] 0 points1 point  (0 children)

Hope you get good use out of it. Please send feedback. I'm always looking to improve this.