SuiteScript 2.x
Automations that hold up under volume.
- Map/Reduce and Scheduled
- Suitelets and Client Scripts
- User Events and validations
Rodolfo Guerra · NetSuite Specialist
I have worked with NetSuite every day for 7 years. Here I share practical notes on development, queries and administration: what works, and the mistakes worth avoiding.
I’m Rodolfo Guerra. I started as a NetSuite administrator at a services company, and today I lead the NetSuite product at a multi-subsidiary company.
My work sits between the business and the system. I listen to what a team needs, turn it into configuration or code, and make sure it keeps working as volume grows.
I built this lab to organize what I learn and share it. Every note comes from a real case.
What I work on day to day.
Automations that hold up under volume.
Clear answers from the data.
A tidy, secure system.
Short notes, each based on a real case. These are the latest.
The five most common mistakes when importing customers via CSV into NetSuite, and how to avoid them.
IntegrationsHow to avoid duplicate orders when an external system retries: idempotency with External ID in a RESTlet.
Best practicesWhy every NetSuite change should go through the sandbox first, and the three-step rule to do it.
SuiteScriptScheduled Script or Map/Reduce: when to use each so your jobs hold up as volume grows.
SuiteQLBUILTIN.DF turns IDs into readable names in SuiteQL with no extra JOIN. Use it for display, not for filtering.
FinanceFrom four places to one flow: paying vendors from NetSuite with Electronic Bank Payments, and what needs a license.
If you work with NetSuite and want to discuss any of these notes, message me on LinkedIn.
Go to my LinkedIn ↗