Are you experiencing dilemmas while generating reports in NetSuite?

In our previous post, we’ve shared a resource to help you solve some of your most-pressing NetSuite questions regarding formulas. It can be found here: A Secret Gold Mine of Information

This resource has helped someone to solve one reporting requirement for their CEO. 

In our next articles, we will be sharing to you a six-part series of tips and tricks to help NetSuite users with their journey in using the account. 

Let’s start with Tip No.1 for NetSuite account owners. 

One of the most common issues we’ve noticed for NetSuite users is generating reports. They are experiencing slowness when saving a record.

Slowness needs proper diagnosis to get the real source of its state. But in our experience, it’s commonly led 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 we’ve generated for a test account, demonstrating how huge the impact is when there’s an After Submit script running in your account.

Generating Reports

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 of generating reports in NetSuite moving forward.

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

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

Stay tuned!

P.S. You can also check this article How to find a NetSuite script that is causing a specific issue or error (no coding involved)

Leave a Reply