Before You Build: Dropdown vs. Multi-Select Custom Fields in SuiteProjects Pro
When setting up a new custom field in NetSuite SuiteProjects Pro, it can be tempting to reach for a multi-select field any time users might need to choose more than one value. There are plenty of valid business reasons to do so. However, multi-select fields currently come with some functional limitations in SPP that dropdown fields don’t have. Knowing about them upfront can save you from rework later and help you set the right expectations with your team from the start.
- Dropdown Fields Can Be Used as Report Filters
Dropdown custom fields can be added as filters when building reports, so you can quickly narrow results to a specific value (for example, only projects where Region = “East”). Multi-select fields can’t be used as report filters, so you would need to pull in all of the data and filter it outside of SPP.
- Dropdown Fields Are Available in More Places Throughout the System
Dropdown fields are available as columns in many more list views than multi-select fields. If your team relies on seeing a field value at a glance in a list view, a dropdown is much more likely to be available there. Multi-select fields are not always an option for list view columns.
- Dropdown Fields Offer More Control in Form Permissions
Dropdown fields can be hidden, made required, or made read-only using form permissions. Multi-select fields can’t be controlled this way. If you need a field to be mandatory on a certain form, or locked down so only certain roles can edit it, a dropdown is the better fit.
(*Note: there is currently an Enhancement Request on file with SPP Support for this; however, it is still unresolved as of the date this article was written)
So, When Should You Use a Multi-Select?
Multi-select fields still have their place. If your business truly needs to capture multiple values for a single record, such as several services or regions that apply to one project, a multi-select may be the right choice. Just be aware of the limitations above so you can plan reports, views, and permissions around them from the beginning.
Bonus Tip: If you’re on the fence, consider whether the “multiple values” need could be met with a dropdown instead, such as a single field with combined options or a few separate dropdown fields, so you can keep the reporting, list view, and form permission functionality.
