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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
Save $30 - limited to first 1,000 registrants
Join the NetSuite community to innovate, connect, and discover what’s next.
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Register now
Join the NetSuite community to innovate, connect, and discover what’s next.
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Register now
{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