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
BUG: Customer Merged With Employee
Someone in our marketing department (who has access to duplicate merging but not employee files) somehow merged two "customers" together thinking they were duplicates -- however, one of the entities was actually an Employee record. I'm not even sure how that can happen since Employee records are not eligible for duplicate merging -- and certainly not with a Customer record.
This has caused several huge problems -- including:
1) exposing transactions that are not normally visible at the customer level
2) marking the customer "inactive" causes the employee file to also go inactive whereby removing from payroll, etc.
3) removing login access from the customer also shuts off the employee access (which is even a bigger problem since the employee record is the Administrator of NS... luckily we had another Admin login to give access back to the employee record)