While most NetSuite instances that I encounter make good use of custom fields, custom forms, and custom subtabs, one of the custom configuration options that I don’t see enough organizations taking advantage of is custom sublists.  Custom sublists are groupings of data from either standard or custom records under a parent record.  Examples of standard sublists include the Transactions list on the customer record, the Related Records list on transactions, and User Notes on an item record.  In this post, I’m going to cover the basics of creating a custom sublist and applying it to a record as well as share a few practical examples of custom sublists that I’ve seen.

NetSuite’s CRM functionality provides support for a multitude of scenarios that may occur during the sales cycle and automatically progresses leads through a series of stages as they hit certain milestones.  For organizations transferring off another CRM system whose users are familiar with that system’s flow and terminology, moving to NetSuite’s native CRM flow can be an adjustment as it may function differently than what their sales staff is accustomed to.  In this blog post, I will be reviewing NetSuite’s standard CRM process flow and following both entity and transaction records as they move through the pipeline to ultimately become customers.

NetSuite releases two system upgrades per year to all accounts, often providing new functionality within existing features in addition to launching brand new capabilities.  Prior to being upgraded to the new release, all accounts are given access to a release preview environment that allows users to preview the changes in a sandbox-like setting.  Detailed documentation describing all changes that are included as part of the new release are also provided at this time and can be accessed from the New Release portlet and in SuiteAnswers.  In this post, I’m going to share the five changes that are being made as part of 2020.2 that I am most excited about.

In my previous blog posts, I’ve highlighted NetSuite’s saved search functionality and shown how you can use them to create dynamic reports to improve visibility into all business areas.  While you can create highly-customized saved searches that use joins to other records, formulas to perform automatic calculations, and even include SQL statements for advanced requirements, there are some instances where saved searches don’t entirely fill an organization’s reporting needs.  In those cases, you can leverage NetSuite’s custom report capabilities in order to bridge the gap.  In this post, I’ll share the basics of report customization in NetSuite and show how standard reports that are already available in your environment can be transformed to align with your specific needs.

The ability to quickly and easily create custom fields in a variety of types in order to meet unique business requirements is one of the things that sets NetSuite apart from other ERP platforms.  In addition to creating checkboxes, open text fields, and date fields, NetSuite also allows users to source custom lists or existing records as drop-down lists using the “List/Record” field type.  In some cases, it is beneficial to give users the ability to select from all available values within the drop-down field.  At times, you may only want to expose a specific sub-set of data in the drop-down list in order to prevent mismatches and make it easier for users to the desired value.  By taking advantage of the Sourcing & Filtering options, you can limit the available values in a List/Record field to only those that apply at the time of entry.  In this blog, I’ll walk through setting up the Sourcing & Filtering options to create dynamic drop-down fields and share a few practical examples of using this functionality.

If you’ve read any of my previous blog posts, you’ve probably gotten a sense of how much I like working with saved searches in NetSuite.  In my opinion, the saved search functionality is one of the most powerful and easy-to-use tools available to NetSuite users; whether you are brand new to NetSuite or are a highly-experienced user with a technical background, you’ll find that saved searches can make accessing data fast and easy.  In this post, we’ll discuss the basics of using Summary Types in saved searches (both as criteria and in the results) and look at a few practical examples that show how you can make use of Summary Types to enhance your searches.

NetSuite releases two system upgrades per year to all accounts, often providing new functionality within existing features in addition to launching brand new capabilities.  Prior to being upgraded to the new release, all accounts are given access to a release preview environment that allows users to preview the changes in a sandbox-like setting.  Detailed documentation describing all changes that are included as part of the new release are also provided at this time and can be accessed from the New Release portlet and in SuiteAnswers.  In this post, I’m going to share the five changes that are being made as part of 2019.2 that I am most excited about.

One of the most under-utilized customization options available within NetSuite is custom records. In fact, the customization-related question that I have heard from users more than any other is “what do people use custom records for?” Although custom records are native NetSuite functionality, many seasoned users haven’t created any and can’t really envision any practical applications for them, especially since NetSuite has such a vast array of standard record types and fields already available. In this post, we’ll take a closer look at the basic functionality and structure of custom records, and we’ll review some real-world applications to help give you some inspiration for ways you can use custom records in your NetSuite environment.