FAgudelo
10/29/2025, 6:20 PMMike Robbins
10/31/2025, 2:14 PMbeforeLoad for a user event script, but doesn't work in a Suitelet? In the Suitelet window appears to be undefined.
form.addButton({
id: 'custpage_cancel',
label: 'Cancel',
functionName: "window.open('" + revenueArrangementUrl + "','_self' );"
});David Na
11/02/2025, 2:58 PM<https://9319243-sb1.extforms.netsuite.com/app/site/hosting/scriptlet.nl?script=1372&deploy=1&custscript_approvalmail_action=approve&custscript_approvalmail_recid=43283>
Even though the Suitelet is set as Available Without Login and the audience is Online Form User, clicking the link returns the error:
Invalid page parameter. Unable to view page.
Has anyone encountered this issue? What is the correct way to send parameters to a Suitelet via email so that non-logged-in users can perform actions?cweier
11/03/2025, 5:21 AMSlackbot
11/05/2025, 4:57 PMSim Greenbaum
11/05/2025, 9:14 PMlet raw = https.get({
url: url,
headers: {
"Content-Type": "application/json",
Authorization: `Bearer ${response_token.access_token}`,
},
});
log.debug("res", { raw, url });Chris
11/05/2025, 10:18 PMStephen Gosner
11/06/2025, 10:24 PMciRecord.setCurrentSublistValue({sublistId : 'line', fieldId : 'amount', value : 0.0});
I receive the following error message...
Value 0.0 outside of valid min/max range for field amount
For additional context, this is a rewrite of the original process and SS 1.0 that created these consolidated invoices via scheduled script, and was able to set the amount line item field to $0. Anyone have an idea of how I can get around this and set the value to $0. I'm able to edit the transaction after it has been created, through the UI and set the value to $0Luke Collins
11/11/2025, 3:15 AMJonathan Allen
11/11/2025, 2:15 PMEllendhula Sreeja
11/12/2025, 6:06 AMMarawan مَرَوَان
11/12/2025, 12:33 PMSim Greenbaum
11/12/2025, 5:53 PMLincecum
11/12/2025, 8:47 PMAn instance of this scheduled script deployment already exists in the work queue.
None of these works ;(Armanda
11/13/2025, 1:31 AMWebberly
11/13/2025, 2:11 PMrequire(['N/currentRecord'], function(currentRecord) {
const record = currentRecord.get();
record.selectLine({
sublistId: 'item',
line: 0
});
const quantityToSet = record.getCurrentSublistValue({
sublistId: 'item',
fieldId: 'quantity'
})
const inventoryDetailSubrecord = record.getCurrentSublistSubrecord({
sublistId: 'item',
fieldId: 'inventorydetail'
});
inventoryDetailSubrecord.selectLine({
sublistId: 'inventoryassignment',
line: 0
});
// this line throws the error "Not supported on current subrecord: CurrentSubrecord.setCurrentSublistValue."
inventoryDetailSubrecord.setCurrentSublistValue({
sublistId: 'inventoryassignment',
fieldId: 'quantity',
value: quantityToSet
});
// Commit the line
inventoryDetailSubrecord.commitLine({
sublistId: 'inventoryassignment'
});
});PF
11/13/2025, 3:34 PMRick Goodrow
11/13/2025, 6:20 PMsearch.lookupFields({
type: record.Type.SALES_ORDER,
id: createdFrom,
columns: [ 'subtotal' ],
});
but getting an error {"type":"error.SuiteScriptError","name":"SSS_INVALID_SRCH_COL","message":"An nlobjSearchColumn contains an invalid column, or is not in proper syntax: subtotal."}
Record Browser shows Sales Order having subtotal as a valid field, and loading the record via record.load() and then using .getValue({fieldId: 'subtotal'}) does actually return the value. So what am I missing?Craig
11/14/2025, 12:19 AM"message": "You have entered an Invalid Field Value false for the following field: isperson",
customerRecord.setValue({fieldId: 'isperson', value: false});
Should I be setting something other than a boolean?eminero
11/14/2025, 9:43 PMSim Greenbaum
11/17/2025, 7:48 PMerror that we received: message: "You can not over-fulfill an item unless you have selected the 'Allow Overage on Item Fulfillments' preference.",
let salerodernumber = data.id;
try {
fulfillmentRecord.save();
} catch (error) {
let message = error.message;
let errodata = {
message: error.message,
info: shipid,
address: address.shipaddress1,
phone: address.phone,
};
log.debug({
title: "create error",
details: { salerodernumber, message, errodata },
});Felix Divall
11/18/2025, 2:29 PMMichael Pope
11/19/2025, 12:00 AMSarim Khan
11/19/2025, 6:54 AMChristopher Quackenbush
11/19/2025, 5:06 PMAaron McCausland
11/19/2025, 11:21 PMtuli
11/20/2025, 10:38 PMif (settlement.paymentTransaction) {
// Handle payment transactions
const lineIndex = bankDepositRecord.findSublistLineWithValue({
sublistId: 'payment',
fieldId: 'id',
value: settlement.paymentTransaction,
});
if (lineIndex != -1) {
bankDepositRecord.selectLine({
sublistId: 'payment',
line: lineIndex,
});
bankDepositRecord.setCurrentSublistValue({
sublistId: 'payment',
fieldId: 'deposit',
value: true,
});
bankDepositRecord.commitLine({ sublistId: 'payment' });
log.debug(
'Line Added to Bank Deposit',
`Payment Transaction: ${settlement.paymentTransaction}, Line Index: ${lineIndex}`
);
} else {
log.error(
'Payment Transaction Not Found in Bank Deposit',
`Payment Transaction ID: ${settlement.paymentTransaction}`
);
}
Tried with large orders, small orders in SBX, works smooth, it’s just PROD that is giving issueItzco
11/21/2025, 10:06 AMMODULE_DOES_NOT_EXIST
error.SuiteScriptError
Module does not exist: /NLRecordScripting.scriptInit$sys.js
Change_form_due_to_entity_changecode: '',
The code is pretty straightforward:
var rec = record.create({
type: context.recordtype
});
setFields(rec, context, ["recordtyle", "sublists", "id"]);
setLists(rec, context);
var recordId = rec.save();
return String(recordId);
All customers use the same forms for Opportunities and for customers. But this seems to be related to Customer record from subsidiaries.
Has anyone experienced something similar? Any clue what this error means?Vishal Chaudhari
11/21/2025, 12:44 PMSim Greenbaum
11/21/2025, 4:57 PM