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
Restrict duplicate custom record
Hi ON community,
I have a custom record linked/set up as a child record of a purchase order (let's call it supplier acknowledgement). I would like to restrict multiple acknowledgements to the same PO (ie. 1 custom record to 1 PO relationship only, cannot be 2 to 1). Is there a way this can be achieved via workflow?
I tried creating a custom field in the PO such that when there is an acknowledgement created against it, it will become ticked (via a set field value workflow). And then second workflow to return user error when creating another acknowledgement when the aforementioned custom field in the PO is ticked. However, the action is on the custom record itself (ie. creating the supplier acknowledgement) whereas the PO is a different record type, hence could not automatically set the custom field value to become ticked whenever a new custom record is created. Any ideas would be much appreciated. Thanks!