NETSUITE-ACADEMY (NS TRAINING, SUPPORT & IMPLEMENTATION)-netsuiteacademy@netsuite-academy.com

The disadvantage of scheduled suitescript 2.0 is that yield script functionality which is there in 1.0 has been taken away. Yield script had a great advantage of being able to resume the script from the point it stopped when time or usage limit exceeded. As netsuite solution provider we provide a Workaround in schedule script 2.0 to overcome time exceeded error is to monitor the time taken to process the script. inIf it reaches near the time limit of 3600s after which script errors out, schedule script can be called again by netsuite customization passing the point at which it needs to resume. For eg: if you are processing 100k records and script is able to process only 50k after 55 mins, then script can be rescheduled by passing the internalid of record from which script needs to process. This internalid is passed in the script parameter. Example code: var startTime = new Date().getTime(); for(var i=0;i<search.length;i++) { var endTime = new Date().getTime(); ...

Subrecord values are retrieved and set in different ways in 1.0 and 2.0. Below examples can be used to understand the difference. Code example for setting Sublist subrecord in 1.0.  Note some variable have not been defined. Define them as per your accounts requirements                       var load_inv = nlapiCreateRecord('inventoryadjustment', {recordmode: 'dynamic'}); load_inv.setFieldValue('account', '1019'); load_inv.setFieldValue('adjlocation', 106); load_inv.setFieldText('custbody_cp_transaction', 'Coating zero parent '); load_inv.setFieldValue('custbody_c_from', recid); load_inv.selectNewLineItem('inventory'); load_inv.setCurrentLineItemValue('inventory', 'item', invadjitm); load_inv.setCurrentLineItemValue('inventory', 'location', 106); load_inv.setCurrentLineItemValue('inventory', 'adjustqtyby', 1); var su...

Values of fields can be sourced dynamically from saved searches. Search result should have only one column in the result and it should have summary. For eg: If you want to source customer's latest sales order date in an custom entity field created for customer record, you can create the search and field as given below: 1) Create a customer search- Make the search public      Criteria: Transaction Type Fields-> Type any of Sales Order           Results: Transaction Type Fields-> Date. Summary type->Maximum and sort the result by the field added in result  Under Available filter tab: Add internal id 2)   Create a Entity Field: Uncheck the store value checkbox. Apply to customer. Under Validation   and defaulting tab, under the saved search selection field, add the search created above                         ...

A lot of times validation is required on submit of a record and developers can get confused on whether to use client script save function or user event before submit function to perform the validation. The below points can be used to make an informed decision. TRIGGER POINT: Client script save is triggered only on create, edit and copy. User event before submit is triggered on create, edit, delete, xedit, approve, reject, cancel (SO, ER, Time Bill, PO & RMA only), pack, ship (IF), markcomplete (Call, Task), reassign (Case), editforecast (Opp, Estimate) Also user event before submit has a type parameter to check the trigger type. Client script save function doesn't have any parameter. To check the trigger type in client script, you will need a pageinit function as well which can be used to copy the type to a global variable which can be accessed on save. USER PERMISSION: A client script can triggered only based on the role permis...

What are scheduled scripts? Scheduled scripts are Netsuite server side scripts used for processing large amount of data/records. What is the governance limit of scheduled scripts? 10000 units. How is a scheduled script executed? Scheduled script can be executed either manually from the script deployment page by clicking on save and execute or it can be executed from the scripts using scheduling api's or it can be scheduled to run at a specific time by defining it's scheduled in the deployment page. Is it possible to overcome 10000 units limit in scheduled script? Yes. This can be achieved in 1.0 script by first checking the remaining usage. If it is less than 200 or 100, you can set the recovery point using nlapiSetRecoveryPoint() and then yielding the script using the api nlapiYieldScript(). In 2.0, there is no option to yield script. You can place back the script in queue when remaining usage is less and pass the internal id of last processed record in the para...

To create a search within any 2.0 script, we need to use search module and using its object create filters and columns and then run it. The following code can be used to create a search in 2.0 define(['N/record', 'N/search'], function(record, search) {         function execute(scriptContext) { var customersearch = search.create({ type: "customer", filters: [                                search.createFilter(                                                                    {                     name: 'isinactive',                     operator: 'is',         ...

An existing search can be loaded or new one can be created in 2.0 script and we can also over come the limitation of just 1000 rows being returned in one execution. Below code can be used for this: var mysearch = search.load({ id: '8888' // enter the existing search id (name or internal id) }); var fil = search.createFilter({ name: 'inactive', operator: 'is', values: false }); mysearch.filters.push(fil); var customersearchResult = mysearch.run().getRange(0, 1000); if(customersearchResult!=null&&customersearchResult!=''&&customersearchResult!=' ') { var completeResultSet = customersearchResult; //copy the result var start = 1000; var last = 2000; while(customersearchResult.length == 1000)//if there are more than 1000 records { customersearchResult = mysearch.run().getRange(start_range, last_range); completeResultSet = completeResultSet.concat(customersearchResult); start = parseFloat(start)+1000; ...