Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
Mainline=T not working --> Transaction.Memo and Transaction.Memo (Main)
I just solved a pesky bug that appeared after our 2009.1 upgrade and thought I would share the solution here in case it helps someone some day.
I had a custom record search with JOINED Transaction fields in the results. I wasn't using any Transaction list fields, just body. I had Mainline = T in the criteria and everything was working fine.
After the upgrade we were getting results for every transaction line, as if Mainline = T was having no effect.
I tried editing the search, experimenting and even recreated it thinking maybe it was corrupted. During this recreation I noticed in the results list:
Steve Klett | Senior Developer
NetValue Technology
0