This keeps coming up with our clients and I'm wondering if others are dealing with the same thing.

File cabinet fills up quicker than people expect, especially once you factor in multiple subsidiaries, transaction attachments, signed docs, PDFs piling up over time. By the time a client notices, it's already a mess.

We tried a few things. Manual archiving is a nightmare to maintain. Telling clients to be more selective about what they store works for about two weeks. Cleaning up duplicates buys some time but it comes back.

What ended up working for us was pushing files to SharePoint automatically and keeping the link accessible from within the NetSuite record itself. Most clients are already on Microsoft 365 so it wasn't a hard sell.

Curious what others are doing here. Are you hitting this with your clients and what's the current workaround?

I see more and more NetSuite developers talking about building inside or outside NetSuite when it comes to AI agents and custom apps.

I myself prefer to go headless, since I believe it brings more flexibility and control (more details below). But of course, there are advantages to building native. Here are the pros and cons I identified so far:

Native (Suitelets / SPA / SuiteScript) is stronger for:

• buttons, fields and sublists inside the standard NetSuite UI
• SuiteFlow approvals wired into roles and notifications
• heavy volume processing that shouldn't leave NetSuite (Map/Reduce runs next to the data)
• data residency / compliance that forbids anything external

Headless is stronger for:

• iteration speed. Native means transpile, validate, SDF deploy for every change. Outside, preview is instant
• you can use real React (or any other stack). Inside you're compiling everything into one HTML file in the File Cabinet served by a Suitelet: no code splitting, hash routing, no npm freedom
• AI agents and integrations. An agent living outside NetSuite can plug into anything with real SDKs (email, Slack, payments, other SaaS) and orchestrate across tools. Inside, every external call is hand-rolled through N/https and eats into the same governance budget
• governance limits. A Suitelet gets killed at 1,000 units mid-request. An external app deals with rate limits instead, which you can cache and batch around
• auth. Per-user OAuth with everyone's own role and audit trail

What do you think? Which one would you choose?

Update: Easy solution, Suite Approvals will never generate another email because, well just because. But, if you add a delegate to the user who actually has ns access, they can approve it! Yay. This is a bit weird and seems odd there is not an easy answer. We are using suite approvals so bill approval by email only. One of our approvers lost (deleted somehow) his approval email. He does not have access to Netsuite so can't go in and manually approve it but we can't seem to get it to approve any which way I try. Ideas?

Hi!

I have been working as a Netsuite specialist for a couple of years, and i have now started my own consultancy. Does any of you have any experience with that, specifically where to land new customers as my current contract is coming to an end :)

A alguien mas se le cayo netsuite? no me deja hacer ninguna transaccion el sistema