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!
Stay in the Know
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Please note that on Friday, March 20, 2026, at 8:00 PM Pacific time, our Case Management System will undergo a scheduled maintenance for approximately 4 hours. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.
Inconsistent behaviour of nlapiSearchRecord
Hi,
I am working on a project to standardize scripts to better support our corporate change management procedures.
One of the items is to update all scripts that utilize nlapiSearchRecord to reference the searchid (e.g. customsearch_active_quotes) instead of the search internal ID (e.g. 5716). This is to allow a more consistent dev, testing and migration process between sandbox and production since internal id's rarely match between systems.
This worked as expected and described in the documentation for my scheduled scripts. However, when I updated a portlet script, the scriptid was not recognized and I am forced to use the internal ID.
0