Configure Solution Area & Deliverable Type

Configure Solution Area and Deliverable Type Picklists

This guide walks you through configuring global picklist value sets for Solution Area and Deliverable Type fields. These configurations enable your Salesforce organization to standardize product categorization and align deliverables with business solutions.

Overview: You will configure two interdependent global picklists, set up field dependencies, and map values across objects to enforce consistent data entry.


Phase 1: Access Picklist Value Sets

Step 1: Navigate to Setup in your Salesforce organization.

Step 2: Search for and open Picklist Value Sets.

Step 3: Locate the following global value sets created by the managed package:

Picklist Value Sets in Salesforce Setup

The Picklist Value Sets section showing available global value sets


Phase 2: Configure Solution Area Picklist

Step 1: Review Packaged Values

Open the Solution Area global value set. You will see example values that were provided by the managed package.

Solution Area packaged example values

Example Solution Area values provided in the managed package

Step 2: Deactivate Unused Values

Deactivate any example values that are not relevant to your business requirements. You can deactivate them one by one without deleting the underlying data.

Tip: Deactivating (rather than deleting) preserves historical data in existing records while hiding unused options from new entries.

Deactivating unused Solution Area values

Deactivating example values that don't match your business needs

Step 3: Add Custom Values

Add new picklist values that align with your business requirements. For example, you might define Solution Area values like:

Important: When adding each value, check the box to automatically add these values to all record types that use this picklist.

Adding custom Solution Area values with record type assignment

Check the option to automatically propagate values to record types

Result: Solution Area Configuration

Your Solution Area picklist now contains active values aligned with your business. In this example, deactivated sample values and added the business solution QuoteX.

Completed Solution Area picklist configuration

Active and inactive values in the configured Solution Area picklist


Phase 3: Configure Deliverable Type Picklist

Follow a similar process for the Deliverable Type global value set. This picklist will be dependent on Solution Area selections.

Step 1: Deactivate Packaged Values

Open the Deliverable Type global value set and deactivate example values that are not applicable to your business.

Deliverable Type packaged values

Example Deliverable Type values provided by the managed package

Step 2: Add Custom Values

Add deliverable types that represent key components of your solutions. For example:

Remember to check the box to automatically add these values to all applicable record types.

Adding custom Deliverable Type values

Custom Deliverable Type values added for QuoteX (Package and Document)

Result: Active and Inactive Values

Your Deliverable Type picklist now shows active custom values and deactivated example values.

Completed Deliverable Type picklist

Active and inactive values in the Deliverable Type picklist


Phase 4: Configure Field Dependencies

Field dependencies ensure that when a Solution Area is selected, only relevant Deliverable Types are available. This enforces data consistency across your organization.

Step 1: Configure Dependencies on Custom Fields

Open each custom field that uses Solution Area and locate the Field Dependencies section that references Deliverable Type.

Field Dependencies section on Solution Area field

Field Dependencies configuration for the Solution Area field

Assign each Solution Area to its applicable Deliverable Types:

Mapping Deliverable Types to Solution Areas

Assigning respective Deliverable Types to each Solution Area value

Step 2: Configure Dependencies on Standard Product Field

Field dependencies can also be set on the standard Product Category field. Configure these dependencies to ensure Solution Area values are available based on product categorization.

Field dependencies on Product Category field

Setting field dependency on the Product Category field

Step 3: Map Solution Area to Product Categories

Navigate to Field Dependencies - Solution Area on the Product (Standard) object.

Field Dependencies for Solution Area on Product object

Accessing Field Dependencies for the Product object

Assign Solution Area values to each Product Category:

Assigning Solution Areas to Product Categories

Mapping Solution Area values to each Product Category value


Configuration Complete

✓ All configurations are now complete
Your Solution Area and Deliverable Type picklists are configured, dependent field values are mapped, and your organization is ready to use these standardized data entry controls.

Users can now select Solution Area values with confidence that available Deliverable Types will be appropriately filtered based on the selected area and product category.

View this article in the article tree to explore related topics