This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

yeah you cant keep triggering the same deployment over and over with UE's

Thanks <@U7XBU8Y3B> any suggestions how to handle such case? Or better approach. We are triggering SS to run some logic behind screen which user doesn't need to keep waiting still that process complete.

um if you dont want the user to wait you could hit a checkbox on the record, and deploy the scheduled to check every 15 minutes for all records with the checkbox, and uncheck it when finished

Depending on the number of deployments/speed of UE save, I've sometimes created an array of deployments and iterate through it until an open dep is found

but that's usually for userinterface actions rather than processing thousands of records that will trigger the UE

Thanks <@U7XBU8Y3B> and <@UA6PZH1Q8> we thought of having schedule script running background and process records on some interval, but after thinking it will keep on executing unnecessarily even if records are not created (though nothing to process) we dropped this idea.
Having multiple depoyments is fine, but depending on how many records are saving there is chance of failing in this case as well as we dont know how much usebase will be there upfront.
Thanks to both of you for your time

Thanks <@U5TF1GQ20>, there won't be any limit on deployments in Netsuite?

not that i know of, although i havent had to find the limit

You can create a new deployment of the scheduled script each time the UE runs. NetSuite will Queue that deployment...

Then at the end of the scheduled process, have the script set its deployment to 'undeployed'.

And have a follow-up process which goes behind and deletes those successfully executed deployments which are undeployed.

I have been running this solution at volume for a couple of years, and it works well.

^^ You have to schedule the newly created deployment so it will run.

Thank you <@U4MF2CN20>. Last point if I understand correctly, do we need to have a scheduled script scheduled to run at interval to clear the executed deployments?

Yes, otherwise the undeployed deployments will stack up.

Optional: in the script process, you can also prevent the script from undeploying itself upon an error condition so that you can investigate any exceptions.

Hi <@U4MF2CN20>, could you please provide sample code for above behavior? How to create deployment from code and clear executed deployments? Thanks in advance.

I don't have a sample right now. You would want to schedule the sch or mr using the task module after you create the deployment using the record module.