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
Matrix items vs. Configurators vs. options I haven't yet considered
I'm a developer hired to work on a NetSuite store for a hardware distributor. We have some complex inventory items to place in our NetSuite store, and we'd like to begin building up the database and templates. On some of our more complex items (e.g. door handles), there are six or so variables - finish/color, backplate, function, etc.
I initially explored matrix items. They provided options, but it appears that items with numerous possible permutations create massive performance issues. (The count on the test case I was trying was ~1300 items -- not past the limit, but close enough for concern). The NetSuite employee post on this thread --
0