Discussions
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Don’t miss your chance to meet our SuiteGurus—NetSuite Support professionals and subject matter experts with extensive experience in select product areas, including OneWorld, Advanced & Basic Accounting, Supply Chain Management, Receivables & Payables, CRM, Account Administration, and the SuiteCloud Platform. Full Conference attendees can prebook exclusive 30-minute one-on-one sessions for your product questions.
Spots are limited! Register through your Agenda Builder and find SuiteGuru under Agenda Enhancements.
If Custom Action loads active record WF fails on itself
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