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
{salesprice} versus {salesPriceHTML} in Matrix items at category level
On the category level we want to have a preview of pricing for our customers (usually the starting price). Using <%=getCurrentAttribute('item','xxxxx')%> works OK where xxxxx is "salesprice" or something like "pricelevel5".
One issue with any price level code that we've tried is MATRIX items.
For example, when the parent prices are left BLANK and all children have prices... then, the template shows "Prices start at <null>".
For example, when the parent prices are irrelevant old pricing and all children have their current accurate prices set... then, the template shows "Prices start at WRONG PRICE". where "WRONG PRICE" is actually one of the old unmanaged prices held in the parent.
0