The logic is triggered from the associated client ...
# releasess
Sergio Ruiz
03/02/2026, 5:32 PMThe logic is triggered from the associated client event, and the error can be seen in the browser console.
n
NElliott
03/04/2026, 1:38 PMAre you using an external or internal url to make the call?
s
Sergio Ruiz
03/04/2026, 1:49 PMInternal, but was old code in 1.0 transformed to 2.0
Copy code
var url = null;
n_search
.create({
type: 'scriptdeployment',
filters: [n_search.createFilter({ name: 'scriptid', operator: n_search.Operator.IS, values: 'customdeploy_x_rem_rl' })],
})
.run()
.each(function (result) {
url = n_record.load({ type: result.recordType, id: result.id }).getValue('url');
return false;
});Sergio Ruiz
03/04/2026, 1:51 PM Copy code
let url = n_url.resolveScript({
scriptId: 'customscript_x_rem_rl',
deploymentId: 'customdeploy_x_rem_rl',
returnExternalUrl: false,
params: params
});
n_https.get.promise({
url: url,
headers: {'User-Agent-x': 'SuiteScript-Call'}n
NElliott
03/04/2026, 1:52 PMI don't usually call RESTlets from inside NS I prefer to use a SuiteLet.
s
Sergio Ruiz
03/04/2026, 1:53 PMYeah. But the thing is, this code is running wihout problem for years. I lwould ike to know what they change internally in 2026.1.
n
NElliott
03/04/2026, 1:54 PMI was going to suggest if you are using an external url then you probably need to look at the external roles and select "Online Form User"
but you are not, so sorry, not sure I know the answer.
s
Sergio Ruiz
03/04/2026, 1:59 PMNo worries, and thank you for your interest. It’s already been resolved, and it turned out to be a legacy issue related to how things were done in 1.0. Now I’m simply curious to understand why it no longer works.
netsuite 1
2 Views