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.
two problems
first one about nlapiScheduleScript: the following code is from the guide,
function updateSalesOrders()
{
var context = nlapiGetContext();
var searchresults = nlapiSearchRecord('salesorder', 'customscript_orders_to_update')
if ( searchresults == null )
return;
for ( var i = 0; i < searchresults.length; i++ )
{
nlapiSubmitField('salesorder', searchresults[i].getId(), 'custbody_approved', 'T')
if ( context.getRemainingUsage() <= 0 && (i+1) < searchresults.length )
{
var status = nlapiScheduleScript(context.getScriptId(), context.getDeploymentId())
if ( status == 'QUEUED' )
break;
}
}
}
here we see that if the usage consumed by the script is not enough, we could schedule another execution. but we are not sure what is the value for i at this time, or we do not know when the execution stops? so i guess the system remembers the breaking point, right? when nlapiScheduleScript is called again, it starts to execute from the interruption?