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!
tranid filter not pulling through
Very strange situation.
I have a client that is using a link to a csv version of a search to export transaction data to Excel. We have done this in many instances to allow for custom transaction formatting not supported by NS.
The link is a custom body HTML field that does not save its value and perpetually has the default value of:
https://system.netsuite.com/app/common/search/searchresults.csv?searchtype=Transaction&Transaction_NUMBERTEXTtype=IS&Transaction_NUMBERTEXT={tranid}&sortcol=Transaction_TRANDATE_raw&sortdir=ASC&csv=Export&OfficeXML=F&style=NORMAL&report=&grid=&searchid=381
For most quotes it generates an export of the data. However all of sudden, is is replacing {tranid} with "To+Be+Generated" as if the field had been created and its value stored before the tranid was assigned. However, this is clearly not the case.