Impact of User Event Scripts

Hi there! It's me again, Lea.

A couple of days ago I posted a resource to help you solve some of your most-pressing NetSuite questions regarding formulas. It can be found here:

https://www.dhirubhai.net/pulse/secret-netsuite-gold-mine-information-lea-celosa-columna/

In fact, one of you messaged me and told me how happy he was able to solve one of the reporting requirements of their CEO.

As promised, I wanted to share with you a six-part series of tips and tricks to help NetSuite users like you with their journey in using the account.

NetSuite Tip for NetSuite account owners # 1:

One of the most common issues I see NetSuite users are reporting is they are experiencing slowness when saving a record.

Slowness needs proper diagnosis to get the real cause but in my experience, it's commonly caused by a User Event Script running on After Submit.

Having After Submit scripts deployed to your account could double or triple the time it takes to save or view it, which may lead to financial loss depending on the severity.

See the screenshot of a simple report I generated for a test account, demonstrating how huge the impact is when there's an After Submit script running in your account.

This data was generated by deploying a User Event script on a Bill transaction containing 50 line items.

Imagine how slow it would be if you've got tons of User Event scripts in your account and you're running a transaction with more line items?

And so.. the best practice is to limit deploying User Event scripts in your account, specifically After Submit context.

How do you do it?

1. Review your account. Are the users reporting the performance issue in a certain transaction?

2. If there is, have a NetSuite technical expert review the scripts deployed to that transaction.

3. Look for After Submit scripts as they're usually the culprit.

4. Check if the scripts belong to NetSuite or a third-party application.

5. Report the issue accordingly.

6. If the script(s) is/are written by another consultant or your in-house developer, then come up with a planned action in optimizing it.

There you go.

This will make sure you and your team won't experience that severe slowness moving forward.

I hope you were able to get value from this post.

In my next topic, I will be discussing another best practice for avoiding a possible data loss.

Stay tuned!