Discussions

Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more

If Custom Action loads active record WF fails on itself

edited Dec 2, 2019 3:40PM in SuiteCloud / Customization 2 comments

We've all seen it happen and it ain't pretty.

Likewise performing an operation in a custom Script Action that causes the active record to be loaded can cause the WF manager to fall apart.

I've been researching why I was receiving logs like this:


26-MAR-2012 15:31:05.327 Initiated workflow
26-MAR-2012 15:31:05.372 Running ONENTRY trigger(Original trigger: SCHEDULED)
26-MAR-2012 15:31:05.390 Enter Scheduled Order Release
26-MAR-2012 15:31:06.099 Running BEFORELOAD trigger
26-MAR-2012 15:31:06.116 Running ONEXIT trigger
26-MAR-2012 15:31:06.117 Transitioning to Complete



Line #4 is where the problem is, the BEFORELOAD trigger should not be fired (IMHO).  It's being caused by a call to nlapiPrintRecord() which I imagine behind the scenes is loading the record that is active in the workflow.  The WF manager then detects this and switches context to deal with the new trigger.

Steve Klett | Senior Developer
NetValue Technology

image-8cb77df5036e1-7e7f.png

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 4 (Oct-Dec 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders