Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
Unexpected Error on ItemSearch
When I attempt to do an ItemSearch on a range of items that are part of a parent-child relationship, I receive an Unexpected Error. For example, the code below will return an Unexpected Error:
ItemSearch itemSearch = new ItemSearch();
itemSearch.setBasic(new ItemSearchBasic());
itemSearch.getBasic().setName(new SearchStringField("1",SearchStringFieldOperator.startsWith));
SearchResult result = null;
try {
result = _port.search(itemSearch);
} catch {
...
However if I change the search constraint from "starting with 1" to "starting with 5" the records are returned properly as one would expect. The difference being my items starting with "1" are grouped using a parent-child relationship and my items starting with "5" have no such relationship. If I further narrow down the search criteria to include just the child items of a parent-child relationship, the search will return results correctly as well. It is only when a parent item is included in the search results that I receive the Unexpected Error.