megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here!
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
No Limits. Just possibilities. Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.

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!

Proposal: abstract super-types

edited Jun 1, 2020 8:47PM in SuiteCloud / Customization 1 comment

If you are familiar with our WS schema, you know that the record types are broken down quite granularly, and that often many groups of record types are very similar.  By "groups" I mean:

* items (InventoryItem, NonInventoryItem, SerializedAssemblyItem, SerializedInventoryItem...)
* entities (Employee, Customer, Contact, Vendor, Partner...)
* events (Task, CalendarEvent...)

Someone on the user group once mentioned they would really appreciate an "Item" type to be defined, which would contain all of the common item fields. 

Where currently the type hierarchy is:

Record    + InventoryItem    + NonInventoryItem    + ...    + Customer    + Partner    + ...


it would become:

Record    + Item    |  + InventoryItem    |  + NonInventoryItem    |  +  ...    |    + Entity    |  + Customer    |  + Partner    |  + ...    |


Pro: could offer the WS users desired flexibility in his or her code.  from an API perspective, eliminating the repititon of common fields would clarify what it is that differentiates similar record types from one another.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders