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!
two issues with nlapiMergeTemplate()
I've encountered two issues with nlapiMergeTemplate that I don't like I wanted to bring them up here to see what you all think... if the behavior should be changed.[LIST=1]
[*]MUST specify a record type and id to perform a merge. This might seem obvious, but there are cases when you would not want to do this (EG: A Task record is not supported with nlapiMergeTemplate (throws UNEXPECTED ERROR) so in order to fill the gap where NetSuite decided to ignore the sendEmail field we need to merge and email on our own - the only LOGICAL record is the task but we can't use it). It seems that since we can pass a custom tag hash we shouldn't be required to specify a valid record.
Steve Klett | Senior Developer
NetValue Technology