Question 286118 in Javascript Question posted in
A very good W3school tutorial can be found here.

Javascript – Efficiently Saving Multiple Records with One Call to Record.save() in SuiteScript

I’m working with SuiteScript and have encountered a scenario where I need to record 20 sales order records. My understanding is that each call to the Record.save() method consumes units, similar to points. This leads me to two questions:

  1. To save 20 sales order records, do I need to call Record.save() 20 times, resulting in a significant consumption of units?
  2. Is there a more efficient way to save these 20 records with a single call to Record.save(), which would reduce the unit cost?

I’m looking for a solution that allows me to save multiple records efficiently without excessively depleting my units. Any insights or alternative methods for handling this in SuiteScript would be greatly appreciated. Thank you!

Tags:

3

Answers


  1. 0

    There is no other way.
    Saving a record consumes units because you are making a change in the database.
    Same as loading a record.
    This is also the reason why search.lookupField and record.submit field as they don’t load or save a full record, consume fewer units.
    If you need to create a sales order, you will use record.create with record.save(). If you need to update a field, you can use the record.submit field.
    Remark: record.submitField doesn’t always work.

    Login or Signup to reply.
  2. 0

    Don’t think of the NetSuite script governance units as something you need to be scared of depleting; think of them as a sanity check against doing something that will cause problems for your users or system. In other words, the governance system is set up to protect you from yourself.

    For example, if your question relates to a User Event or Client script, saving 20 sales orders will cause a long delay whenever it’s fired, and that would not even (by itself) cause a governance exceeded error. (Record.save() uses 20 units per invocation, so 400 total. Including the units from loading or creating wopuld have you up to 600 – still well below the 1000 unit total allowed.)

    To answer your question, you would need to call Record.save() once for each record, as it is a method on the Record instance object. There is no SuiteScript API, for example, which accepts an array of Record objects and saves them all.

    There are several options for improving performance, depending on your specific use case:

    1. If you only need to update body level fields which support inline editing, you can use record.submitFields(). This will be more performant and use half the governance units, compared with loading and saving.
    2. If using a client script, I wouldn’t recommend saving 20 records from within a client script but you can use Record.save.promise() to enable your flow to continue while the records save asynchronously. This would still use the same amount of governance units, but may significantly improve user experience.
    3. For either client or user event, you can save the relevant data to a custom record or text file (EG: as JSON data), and then call a Scheduled or Map/Reduce script to complete the bulk of the work. In this scenario, your client or user event would save the data, and then schedule the Scheduled or Map/Reduce script using the N/task module. The record or file to be processed by the scheduled script can be passed as a script parameter or discovered using a predefined flag (field) on the custom record, or retrieved from a specified folder if using a file.
    Login or Signup to reply.
  3. 0

    20 saleorder = 200 units in the scenario where you call .save() in each of them.

    An alternative is import a CSV via suitescript and call the csv import and create many saleorder as you want

    • Import CSV to file cabinet= 0 Units

    • Import Taks CSV Import =100 Units no matther how many saleorder you create.

    The script will run fast and no need to wait to suitescript finish to save the all records. But you dont need to worry about the units usage, I´ll more worried if you have beforesubmit and aftersubmit scripts in saleOrder transaction and those add seconds before the document is saved that will cause you problems because you will get request timeout errors and thats a headhache

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search