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
Custom transaction links do not behave the same as native transaction links in saved searches
NOTE: This is not a question. Instead, I'm sharing something I learned recently from a NS Support case.
Summary: If you want to include one or more fields from a record referenced by a transaction link in saved search results, a criteria must be included to limit results where Main Line of the transaction link is true, even though this criteria is not needed when using native transaction links.
As an example, we have a custom transaction link field on invoice records for invoices generated in a system outside of NetSuite. This transaction link, named IO Related SO, references a sales order, exactly like the standard Created From field.
0