Discussions
Join the NetSuite community to innovate, connect, and discover what’s next.
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Register now
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?