Track Customer Deposit Balances

Start with required opening lines

JSDoc comments and a define function are required at the top of the script file. The JSDoc comments in this script indicate that it is a SuiteScript 2.1 user event script. The script uses three SuiteScript modules specified in the define statement:

• N/record -allows you to work with NetSuite records

• N/search – allows you to create and run on-demand or saved searches and analyze and iterate through the search results

• N/log – allows you to log execution details

Start a new script file using any text editor and place the following JSDoc comments and define function at the top of the file:

                /**
 * @NApiVersion 2.1
 * @NScriptType UserEventScript
 * @NModuleScope SameAccount
 */

define(['N/record', 'N/search', 'N/log'], (record, search, log) => {
}); 

              

Create the entry point function

This script is triggered on the afterSubmit entry point when a sales order is saved.

Add the following function definition at the top of the define function:

                function afterSubmit(scriptContext) {
} 

              

Load the new sales order record

This section of the script loads the new sales order record.

Add the following code at the top of the afterSubmit entry point function:

                const contextOrder = scriptContext.newRecord;
const soID = contextOrder.id;
const salesorder = record.load({
    type: record.Type.SALES_ORDER,
    id: soID
}); 

              

Get values from the new sales order record

This section of the script gets values from the sales order and loads the saved search.

Add the following code within the afterSubmit entry point function:

                const soTotal = salesorder.getValue({
    fieldId: 'total'
});
const soEntity = salesorder.getValue({
    fieldId: 'entity'
});
const soTranId = salesorder.getValue({
    fieldId: 'tranid'
});
const soFullTextTranID = 'Sales Order #'+soTranId;
const mySearch = search.load({
    id: 'customsearch_sobalancedue'
}); 

              

Create and apply filters for your saved search

This section of the script creates filters and applies them to your saved search.

Add the following code within the afterSubmit entry point function:

                const entityFilter = search.createFilter({
    name: 'entity',
    operator: search.Operator.ANYOF,
    values: soEntity
});
const soIdFilter = search.createFilter({
    name: 'formulatext',
    operator: search.Operator.IS,
    formula: "CASE WHEN {type}='Customer Deposit' then {appliedtotransaction} when {type}='Deposit Application' then {createdfrom.salesorder} when {type}='Sales Order' then 'Sales Order #'||{number} end",
    values: soFullTextTranID
});
mySearch.filters.push(entityFilter, soIdFilter); 

              

Run the saved search and process the results

The last section of the script calculates the balance remaining on the sales order using the total current value of the sales order and the total paid value from the saved search. It then sets the custom fields with the corresponding values and saves the updated sales order. When the user sees the saved sales order, the values are populated in the Total Deposit Paid and Remaining Balance fields.

Add the following code within the afterSubmit entry point function:

                const soresults = mySearch.run();
mySearch.run().each(function(soresults) {
    let soTextID = soresults.getValue({
        name: 'formulatext',
        summary: search.Summary.GROUP
    });
    if (soFullTextTranID === soTextID) {
        let totalPaid = soresults.getValue({
            name: 'formulacurrency',
            summary: search.Summary.SUM
        });
        let remainingBalanceOnOrder = parseFloat(parseFloat(soTotal))-parseFloat(totalPaid);
        salesorder.setValue({
            fieldId: 'custbody_total_deposit_paid',
            value: totalPaid
        });
        salesorder.setValue({
            fieldId: 'custbody_balance_remaining',
            value: remainingBalanceOnOrder
        });
        let id = salesorder.save({
            enableSourcing: true,
            ignoreMandatoryFields: true
        });
    }
}); 

              

Create the return statement

This script associates the afterSubmit function with the afterSubmit user event script entry point.

Add the following code immediately above the closing }); in your script:

                return {
    afterSubmit: afterSubmit
}; 

              

Save your script file

You need to save your script file so you can load it to the NetSuite File Cabinet. Before you save your script file, you may want to adjust the indentation so that the script is readable. Refer to The Complete Script for suggested indentation.

When you are happy with how your script file reads, save it as a .js file (for example, ue_set_custom_fields.js).

Start with required opening lines

JSDoc comments and a define function are required at the top of the script file. The JSDoc comments in this script indicate that it is a SuiteScript 2.1 user event script. The script uses three SuiteScript modules specified in the define statement:

• N/record -allows you to work with NetSuite records

• N/search – allows you to create and run on-demand or saved searches and analyze and iterate through the search results

• N/log – allows you to log execution details

Start a new script file using any text editor and place the following JSDoc comments and define function at the top of the file:

                /**
 * @NApiVersion 2.1
 * @NScriptType UserEventScript
 * @NModuleScope SameAccount
 */

define(['N/record', 'N/search', 'N/log'], (record, search, log) => {
}); 

              

Create the entry point functions

This script is triggered on the beforeSubmit and afterSubmit entry points when a sales order is saved.

Add the following function definitions at the top of the define function:

                function beforeSubmit(scriptContext) {
}
function afterSubmit(scriptContext) {
} 

              

Get the new deposit record and check the event type

The section of the script gets the value of the sales order the customer deposit is created from. If the customer deposit is created from a sales order and is being deleted, it updates the amount deposited and amount remaining on the related sales order.

This section of the script is executed after the customer deposit is saved but before it is submitted to the database using the beforeSubmit entry point. Add the following code at the top of the beforeSubmit entry point function:

                const contextDep = scriptContext.newRecord;
const soID = contextDep.getValue({
    fieldId: 'salesorder'
});
if ((soID !== null) && (scriptContext.type === scriptContext.UserEventType.DELETE)) {
} 

              

Get values from the sales order if it isn’t in Billed status

This section of the script loads the sales order, checks to see if it is in Billed status, and if it is not in Billed status, sets values on the custom fields on the sales order based on a deposit and the calculated balance remaining.

Add the following code within the if statement of the beforeSubmit entry point function:

                const depAmt = contextDep.getValue({
    fieldId: 'payment'
});
const salesorder = record.load({
    type: record.Type.SALES_ORDER,
    id: soID
});
const status = salesorder.getValue({
    fieldId: 'status'
});
if (status !== 'Billed') {
    const soTotalPaid = salesorder.getValue({
        fieldId: 'custbody_total_deposit_paid'
    });
    const soRemainingBalance = salesorder.getValue({
        fieldId: 'custbody_balance_remaining'
    });
    salesorder.setValue({
        fieldId: 'custbody_total_deposit_paid',
        value: soTotalPaid - depAmt
    });
    salesorder.setValue({
        fieldId: 'custbody_balance_remaining',
        value: (soRemainingBalance + depAmt)
    });
    const id = salesorder.save({
        enableSourcing: true,
        ignoreMandatoryFields: true
    });
} 

              

Make sure the sales order ID is valid and the the user is creating or editing the record

This section of the script makes sure the record is valid and the user is not viewing the order, but is creating or editing it.

Add the following code at the top of the afterSubmit entry point function:

                const contextDep = scriptContext.newRecord;
const soID = contextDep.getValue({
    fieldId: 'salesorder'
});
if ((soID !== null) && ((scriptContext.type === scriptContext.UserEventType.CREATE) || (scriptContext.type === scriptContext.UserEventType.EDIT))) {
} 

              

Get the sales order status

This section of the script loads the sales order, checks to see if it is in Billed status (the status determines whether the saved search is run).

Add the following code within the if statement:

                const salesorder = record.load({
    type: record.Type.SALES_ORDER,
    id: soID
});
const status = salesorder.getValue({
    fieldId: 'status'
});
if (status !== 'Billed') {
} 

              

Create and apply filters for your saved search

This section of the script loads the saved search to match the order related to the customer deposit to the order in the search results. The saved search uses formulas because the relationship of a customer deposit or customer refund to a sales order can take different paths.

Add the following code within the nested if statement:

                const soEntity = salesorder.getValue({
    fieldId: 'entity'
});
const soTranId = salesorder.getValue({
    fieldId: 'tranid'
});
const soFullTextTranID = 'Sales Order #' + soTranId;
const mySearch = search.load({
    id: 'customsearch_sobalancedue'
});
const entityFilter = search.createFilter({
    name: 'name',
    operator: search.Operator.IS,
    values: soEntity
});
const soIdFilter = search.createFilter({
    name: 'formulatext',
    operator: search.Operator.IS,
    summary: search.Summary.MAX,
    formula: "CASE WHEN {type}='Customer Deposit' then {appliedtotransaction} when {type}='Deposit Application' then {createdfrom.salesorder} when {type}='Sales Order' then 'Order #'||{number} end",
    values: soFullTextTranID
});
mySearch.filters.push(entityFilter, soIdFilter); 

              

Run the search and process the results

This section of the script gets the balances from the saved search and sets the custom fields on the sales order that the customer deposit was created from.

Add the following code within the nested if statement:

                const soresults = mySearch.run();
mySearch.run().each(function(soresults) {
    let soTextID = soresults.getValue({
        name: 'formulatext',
        summary: search.Summary.GROUP
    });
    if (soFullTextTranID === soTextID) {
        let totalPaid = soresults.getValue({
            name: 'formulacurrency',
            summary: search.Summary.SUM
        });
        let soTotal = salesorder.getValue({
            fieldId: 'total'
        });
        let remainingBalanceOnOrder = parseFloat(soTotal)-parseFloat(totalPaid);
        salesorder.setValue({
            fieldId: 'custbody_total_deposit_paid',
            value: totalPaid
        });
        salesorder.setValue({
            fieldId: 'custbody_balance_remaining',
            value: remainingBalanceOnOrder
        });
        let id = salesorder.save({
            enableSourcing: true,
            ignoreMandatoryFields: true
        });
    }
}); 

              

Create the return statement

This script associates the beforeSubmit function with the beforeSubmit user event script entry point and the afterSubmit function with the afterSubmit user event script entry point.

Add the following code immediately above the closing }); in your script:

                return {
    beforeSubmit: beforeSubmit,
    afterSubmit: afterSubmit
}; 

              

Save your script file

You need to save your script file so you can load it to the NetSuite File Cabinet. Before you save your script file, you may want to adjust the indentation so that the script is readable. Refer to The Complete Script for suggested indentation.

When you are happy with how your script file reads, save it as a .js file (for example, ue_update_custom_fields.js).

Start with required opening lines

JSDoc comments and a define function are required at the top of the script file. The JSDoc comments in this script indicate that it is a SuiteScript 2.1 user event script. The script uses three SuiteScript modules specified in the define statement:

• N/record -allows you to work with NetSuite records

• N/search – allows you to create and run on-demand or saved searches and analyze and iterate through the search results

• N/log – allows you to log execution details

Start a new script file using any text editor and place the following JSDoc comments and define function at the top of the file:

                /**
 * @NApiVersion 2.1
 * @NScriptType UserEventScript
 * @NModuleScope SameAccount
 */

define(['N/record', 'N/search', 'N/log'], (record, search, log) => {
}); 

              

Create the entry point function

This script is triggered on the afterSubmit entry points when a sales order is saved.

Add the following function definition at the top of the define function:

                return {
    afterSubmit: function(scriptContext) {
        const contextRef = scriptContext.newRecord;
        const refId = contextRef.id;
        UpdateSalesOrder(refId);
    }
}; 

              

Create the UpdateSalesOrder function

This script uses a function to update the sales order. This function is called from the afterSubmit entry point function.

Add the following code after the end of the return statement:

                function UpdateSalesOrder(refId) {
} 

              

Load the customer refund

This section of the script loads the customer refund and gets the values for the total amount of the refund and the number of lines, or number of transactions, the refund is applied to.

Add the following code at the top of the UpdateSales Order function:

                const refund = record.load({
    type: record.Type.CUSTOMER_REFUND,
    id: refId,
    isDynamic: true
});
const soEntity = refund.getValue({
    fieldId: 'customer'
});
const lines = refund.getLineCount({
    sublistId: 'apply'
}); 

              

Add a for loop

This section of the script uses a for loop to iterate through each deposit application associated with the customer refund and gets the amount applied.

Add the following code within the UpdateSalesOrder function:

                for (let i = 0; i < lines; i++) {
} 

              

Get the deposit number and the refund amount

For each deposit application associated with the customer refund, this script gets the deposit number and the refund amount from the refund.

Add the following code at the top of the for loop:

                let depositnum = refund.getSublistText({
    sublistId: 'apply',
    fieldId: 'internalid',
    line: i
});
let refundamt = refund.getSublistValue({
    sublistId: 'apply',
    fieldId: 'amount',
    line: i
}); 

              

Find the linked sales order

This section of the script looks up the fields on each deposit application to find the linked sales order and the total of the sales order.

Add the following code within the for statement:

                let order = search.lookupFields({
    type: search.Type.DEPOSIT_APPLICATION,
    id: depositnum,
    columns: 'createdfrom.salesorder'
});
let soFullTextTranID = order['createdfrom.salesorder'][0].text;
let orderId = order['createdfrom.salesorder'][0].value;
let soTotalPaid = search.lookupFields({
    type: search.Type.SALES_ORDER,
    id: orderId,
    columns: ['total']
});
let soTotal = soTotalPaid['total']; 

              

Load the saved search

This section of the script loads the saved search to get the current balance of the deposits and gift certificates paid toward the sales order, less the amount of any refunds applies.

Add the following code within the for statement:

                let mySearch = search.load({
    id: 'customsearch_sobalancedue'
}); 

              

Create and apply search filters for you saved search

This section of the script creates and applies two search filters for your saved search.

Add the following code within the for statement:

                let entityFilter = search.createFilter({
    name: 'internalid',
    join: 'customer',
    operator: search.Operator.EQUALTO,
    summary: search.Summary.MAX,
    values: soEntity
});
let soIdFilter = search.createFilter({
    name: 'formulatext',
    operator: search.Operator.IS,
    formula: "CASE WHEN {type}='Customer Deposit' then {appliedtotransaction} when {type}='Deposit Application' then {createdfrom.salesorder} when {type}='Sales Order' then 'Sales Order #'||{number} end",
    values: soFullTextTranID
});
mySearch.filters.push(entityFilter, soIdFilter); 

              

Run the search and process the results

This section of the script loads each related sales order and sets the new vales for total paid and remaining balance amounts.

Add the following code within the for statement:

                let soresults = mySearch.run();
mySearch.run().each(function(soresults) {
    let soTextID = soresults.getValue({
        name: 'formulatext',
        summary: search.Summary.GROUP
    });
    if (soFullTextTranID === soTextID) {
        let totalPaid = soresults.getValue({
            name: 'formulacurrency',
            summary: search.Summary.SUM
        });
        let remainingBalanceOnOrder = parseFloat(soTotal);
        remainingBalanceOnOrder = parseFloat(remainingBalanceOnOrder)-parseFloat(totalPaid);
        let salesorder = record.load({
            type: record.Type.SALES_ORDER,
            id: orderId,
            isDynamic: true
        });
        salesorder.setValue({
            fieldId: 'custbody_total_deposit_paid',
            value: totalPaid
        });
        salesorder.setValue({
            fieldId: 'custbody_balance_remaining',
            value: remainingBalanceOnOrder
        });
        let id = salesorder.save({
            enableSourcing: true,
            ignoreMandatoryFields: true
        });
    }
}); 

              

Create the return statement

In this script, the return statement was included when you added the entry point function at the top of the define function (see Create the entry point function).

Save your script file

You need to save your script file so you can load it to the NetSuite File Cabinet. Before you save your script file, you may want to adjust the indentation so that the script is readable. Refer to The Complete Script for suggested indentation.

When you are happy with how your script file reads, save it as a .js file (for example, ue_handle_refund.js).

Start with required opening lines

JSDoc comments and a define function are required at the top of the script file. The JSDoc comments in this script indicate that it is a SuiteScript 2.1 user event script. The script uses three SuiteScript modules specified in the define statement:

• N/record -allows you to work with NetSuite records

• N/search – allows you to create and run on-demand or saved searches and analyze and iterate through the search results

• N/log – allows you to log execution details

Start a new script file using any text editor and place the following JSDoc comments and define function at the top of the file:

                /**
 * @NApiVersion 2.1
 * @NScriptType UserEventScript
 * @NModuleScope SameAccount
 */

define(['N/record', 'N/search', 'N/log'], (record, search, log) => {
}); 

              

Create the entry point function

This script is triggered on the beforeSubmit and afterSubmit entry points when a sales order is saved.

Add the following function definition at the top of the define function:

                function afterSubmit(scriptContext) {
} 

              

Get values for the related customer and customer deposit

This section of the script loads the previous version of the deposit application in case it has been deleted so that it can get the values of the related customer and customer deposit.

Add the following code within the afterSubmit entry point script:

                const contextDepApp = scriptContext.oldRecord;
const depAppId = contextDepApp.id;
const soEntity = contextDepApp.getValue({
    fieldId: 'customer'
});
const createdFrom = contextDepApp.getValue({
    fieldId: 'deposit'
});
const cusDeposit = record.load({
    type: record.Type.CUSTOMER_DEPOSIT,
    id: createdFrom,
    isDynamic: true
});
const orderId = cusDeposit.getValue({
    fieldId: 'salesorder'
});
const soFullTextTranID = cusDeposit.getText({
    fieldId: 'salesorder',
}); 

              

Load the saved search and create and apply search filters

This section of script loads the saved search you created and adds filters to find the sales order related to the deposit application along with the values for its current total deposited.

Add the following code within the afterSubmit entry point script:

                const mySearch = search.load({
    id: 'customsearch_sobalancedue'
});
const entityFilter = search.createFilter({
    name: 'internalidnumber',
    operator: search.Operator.IS,
    values: soEntity
});
const soIdFilter = search.createFilter({
    name: 'formulatext',
    operator: search.Operator.IS,
    formula: "CASE WHEN {type}='Customer Deposit' then {appliedtotransaction} when {type}='Deposit Application' then {createdfrom.salesorder} when {type}='Sales Order' then 'Sales Order #'||{number} end",
    values: soFullTextTranID
});
mySearch.filters.push(entityFilter, soIdFilter); 

              

Run the search and process the results

This section of script runs the saved search you created find the sales order related to the deposit application along with the values for its current total deposited.

Add the following code within the afterSubmit entry point script:

                const soresults = mySearch.run();
mySearch.run().each(function(soresults) {
    let soTextID = soresults.getValue({
        name: 'formulatext',
        summary: search.Summary.GROUP
    });
    if (soFullTextTranID === soTextID) {
    }
}); 

              

Load the sales order and set values

This section of the script loads the sales order related to the deposit application and sets the values for the deposit paid and new remaining balance based on the values returned from the saved search.

Add the following code within the if statement:

                let totalPaid = soresults.getValue({
    name: 'formulacurrency',
    summary: search.Summary.SUM
});
let salesorder = record.load({
    type: record.Type.SALES_ORDER,
    id: orderId,
    isDynamic: true
});
let soTotal = salesorder.getValue({
    fieldId: 'total'
});
let remainingBalanceOnOrder = parseFloat(soTotal);
remainingBalanceOnOrder = parseFloat(remainingBalanceOnOrder) - parseFloat(totalPaid);                
salesorder.setValue({
    fieldId: 'custbody_total_deposit_paid',
    value: totalPaid
});
salesorder.setValue({
    fieldId: 'custbody_balance_remaining',
    value: remainingBalanceOnOrder
});
let id = salesorder.save({
    enableSourcing: true,
    ignoreMandatoryFields: true
}); 

              

Create the return statement

This script associates the afterSubmit function with the afterSubmit user event script entry point.

Add the following code immediately above the closing }); in your script:

                return {
    afterSubmit: afterSubmit
}; 

              

Save your script file

You need to save your script file so you can load it to the NetSuite File Cabinet. Before you save your script file, you may want to adjust the indentation so that the script is readable. Refer to The Complete Script for suggested indentation.

When you are happy with how your script file reads, save it as a .js file (for example, ue_handle_deposit.js).

To create the script record for the Set Custom Fields user event script:

1. Upload your script to the NetSuite File Cabinet.

2. Go to Customization > Scripting > Scripts > New.

3. Select your script from the Script File list and click Create Script Record. The Script page is displayed.

4. On the Script page, enter the following values:

   Field	Value
   Name	Deposit Balance Set Custom Fields
   ID	_ue_depBalance_set_fields NetSuite prepends ‘customscript’ to this ID.
   Description	This script sets the custom fields on a sales order record when the user saves the sales order.

5. Optionally set any other fields on the script record as desired.

6. Click Save.

To create the script record for the Update Custom Fields user event script:

1. Upload your script to the NetSuite File Cabinet.

2. Go to Customization > Scripting > Scripts > New.

3. Select your script from the Script File list and click Create Script Record. The Script page is displayed.

4. On the Script page, enter the following values:

   Field	Value
   Name	Deposit Balance Update Custom Fields
   ID	_ue_depBalance_update_fields NetSuite prepends ‘customscript’ to this ID.
   Description	This script updates the custom fields on a sales order record when a user loads or saves a sales order.

5. Optionally set any other fields on the script record as desired.

6. Click Save.

To create the script record for the Handle Refund user event script:

1. Upload your script to the NetSuite File Cabinet.

2. Go to Customization > Scripting > Scripts > New.

3. Select your script from the Script File list and click Create Script Record. The Script page is displayed.

4. On the Script page, enter the following values:

   Field	Value
   Name	Deposit Balance Handle Refund
   ID	_ue_depBalance_refund NetSuite prepends ‘customscript’ to this ID.
   Description	This script updates the sales order if a refund has been issued.

5. Optionally set any other fields on the script record as desired.

6. Click Save.

To create the script record for the Handle Deletion of Deposit Application user event script:

1. Upload your script to the NetSuite File Cabinet.

2. Go to Customization > Scripting > Scripts > New.

3. Select your script from the Script File list and click Create Script Record. The Script page is displayed.

4. On the Script page, enter the following values:

   Field	Value
   Name	Deposit Balance Deletion of Deposit App
   ID	_ue_depBalance_delete_depApp NetSuite prepends ‘customscript’ to this ID.
   Description	This script handles the deletion of a deposit application that is associated with a customer refund or customer deposit when a user saves a sales order.

5. Optionally set any other fields on the script record as desired.

6. Click Save.

To deploy the Set Custom Fields user event script:

1. Complete the steps in Step 6: Create the Script Records for your user event script.

2. Go to Customization > Scripting > Scripts.

3. Find your user event script in the list of scripts and click Deployments. The Script Deployments page appears.

4. Click New Deployment. The Script Deployment page appears.

5. On the Script Deployment page, enter the following values:

   Field	Value
   Applies To	Sales Order
   ID	_ue_deposit_track_so NetSuite prepends 'custdeploy' to this ID.
   Status	Testing The Testing status allows the script owner to test the script without affecting other users in the account.
   Log Level	Debug The Debug level will write all log.debug statements in the script to the Execution Log tab of the script deployment record as well as all errors.
   Execute As Role	Current Role It is normally best practice to have scripts execute with the user’s current role to avoid granting unwanted access.
   Audience > Roles	Check Select All

6. Click Save.

To deploy the Update Custom Fields user event script:

1. Complete the steps in Step 6: Create the Script Records for your user event script.

2. Go to Customization > Scripting > Scripts.

3. Find your user event script in the list of scripts and click Deployments. The Script Deployments page appears.

4. Click New Deployment. The Script Deployment page appears.

5. On the Script Deployment page, enter the following values:

   Field	Value
   Applies To	Customer Deposit
   ID	_ue_customer_deposit NetSuite prepends 'custdeploy' to this ID.
   Status	Testing The Testing status allows the script owner to test the script without affecting other users in the account.
   Log Level	Debug The Debug level will write all log.debug statements in the script to the Execution Log tab of the script deployment record as well as all errors.
   Execute As Role	Current Role It is normally best practice to have scripts execute with the user’s current role to avoid granting unwanted access.
   Audience > Roles	Check Select All

6. Click Save.

To deploy the Handle Refund user event script:

1. Complete the steps in Step 6: Create the Script Records for your user event script.

2. Go to Customization > Scripting > Scripts.

3. Find your user event script in the list of scripts and click Deployments. The Script Deployments page appears.

4. Click New Deployment. The Script Deployment page appears.

5. On the Script Deployment page, enter the following values:

   Field	Value
   Applies To	Customer Refund
   ID	_ue_customer_refund NetSuite prepends 'custdeploy' to this ID.
   Status	Testing The Testing status allows the script owner to test the script without affecting other users in the account.
   Log Level	Debug The Debug level will write all log.debug statements in the script to the Execution Log tab of the script deployment record as well as all errors.
   Execute As Role	Current Role It is normally best practice to have scripts execute with the user’s current role to avoid granting unwanted access.
   Audience > Roles	Check Select All

6. Click Save.

To deploy the Handle Deletion of Deposit Application user event script:

1. Complete the steps in Step 6: Create the Script Records for your user event script.

2. Go to Customization > Scripting > Scripts.

3. Find your user event script in the list of scripts and click Deployments. The Script Deployments page appears.

4. Click New Deployment. The Script Deployment page appears.

5. On the Script Deployment page, enter the following values:

   Field	Value
   Applies To	Deposit Application
   ID	_ue_deposit_application NetSuite prepends 'custdeploy' to this ID.
   Status	Testing The Testing status allows the script owner to test the script without affecting other users in the account.
   Log Level	Debug The Debug level will write all log.debug statements in the script to the Execution Log tab of the script deployment record as well as all errors.
   Execute As Role	Current Role It is normally best practice to have scripts execute with the user’s current role to avoid granting unwanted access.
   Audience > Roles	Check Select All

6. Click Save.

• SuiteCloud Customization Tutorials
• Add Custom Button to Execute a Suitelet
• Calculate Commission on Sales Orders
• Copy a Value to the Item Column
• Disable Tax Fields
• Hide a Column in a Sublist
• Populate Item Substitution
• Set a Default Posting Period in a Custom Field
• Set Purchase Order Exchange Rate
• Set the Item Amount to Zero for Marketing Orders
• Set Default Values in a Sublist
• Validate Order on Entry