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!
Current Inventory
Hello,
We have built an order fulfillment application that creates assembly build/unbuild and item fulfillment records via SuiteTalk for serialized assembly item sales orders.
With RMA units, we often sell them as part of a different serialized assembly item. (We use the same type of physical item in multiple products.)
One of the requirements is to handle RMA units with minimal effort for the user. That means the application has to detect when a RMA serial number is scanned so that it can create the necessary assembly unbuild record before creating the assembly build record.
Currently we are achieving this by keeping our own database that essentially tracks serial numbers and what type of serialized assembly item they were last used in, if any. It is not pretty, and my current challenge is to optimize this process so that we can depend as much as possible on the SuiteTalk API instead of a local database.