Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
Data Corruption in Escalation Records
I'm writing an alternative escalation system to NetSuite's, in order to cut escalation times down. It uses a custom record to define the escalation tree, and then inserts new employee records into the escalation sublist in the case based on that tree. However, I'm finding that when I run the code, the escalation sublist isn't in the same order as it was written on the last execution of the code, which breaks the escalation code since its history is lost. Below is an extracted piece of script that demonstrates the problem, along with the debug log that shows that between
0