This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

Hi, I have a suitelet and it does some operation on sales order what I want is to reload the same SO on which I do the operation after I call the suitelet through a button. how can we do that?

<https://developer.mozilla.org/en-US/docs/Web/API/Location/reload|Location: reload()>

where do I have to write this location.reload()?

I’m not using any client script in this case

nope. I’ve added it on beforeLoad of UE

the code in the button still runs clientside

use N/redirect module and in POST
you can use, i did it..it worked cool
```redirect.toRecord({ type: record.Type.TASK, id: taskRecordId, parameters: { 'custparam_test':'helloWorld' } });```

but in my suitelet I’m not submitting anything

refer this for using a UE button to connect to client to suitelet, and try as battk suggested

Add a Button on the Employee Record That Will Generate a PDF via SuteScript 2.0 - below

<https://netsuite.custhelp.com/app/answers/detail/a_id/93513/kw/call%20suitelet>

hey it worked <@U01HNT55AV6> thanks for this. I have one last question. Can we add delay in the reload time of the sales order. I mean when we click on the button the client is getting fired then suitelet is getting fired in this time the record is pushed to database and it comes back to client. The changes are not reflecting immediately.

if you talking about changes not reflecting immediately, i think thats related to netsuites performance.. if you want to add delay  i am not sure

I see. I got something called as setTimeout() which adds delay in CL

most of the client side apis have asynchronous versions which allow you to run code after the request is finished

you dont need to guess when the request is complete

Async would work better.  With setTimeout() you run the risk of not allowing enough time for NetSuite to save the records or forcing the user to wait for a very long extended amount of time. Neither scenario is good.