Skip to main content

Bulk Delete for Picklist Field Values (CRM)

You can now select multiple picklist values and remove them all at once using the same replacement flow as single deletions. Records using a deleted value are automatically migrated to a replacement you choose — no data loss, no one-at-a-time slowdown.

1. Before You Start

You will need:

● An administrator account on your CRM instance.

● A picklist field with at least a few values you want to remove.

● A clear idea of which existing values should replace the deleted ones on any records that currently use them.

Access requirements: Only users with permission to access CRM Settings →

Module Management → Picklist Field Values can use this feature. This is normally limited to System Administrators.

If you don't see the Picklist Field Values menu item, you don't have the required permissions. Ask your CRM administrator or contact Dazos support to enable access for your account.

2. Open the Picklist Field Values Screen

From the CRM, navigate to:

Settings → CRM Settings → Module Management → Picklist Field Values

On this screen you'll see two dropdowns at the top:

Dropdown

Purpose

Select

Module

Pick the module whose picklist you want to edit (for example, Leads, Accounts, Therapist Requested).

Select

Picklist

Pick the specific picklist field within that module (for example, Lead Source, Sales Stage, Therapist Requested Values).

Once both are selected, the list of current picklist values appears.

3. Select the Values You Want to Delete

Each row in the picklist value table now has a checkbox on the left, next to the drag handle.

● Click a checkbox to mark that value for deletion.

● Click it again to clear the selection.

● You can select as many values as you need — across the visible list — before deleting.

4. Use the Bulk Delete Toolbar

As soon as you tick the first checkbox, a small toolbar appears above the table:

Element

What it shows/does

Count badge

The number of values you have currently selected (for example, 3 selected).

Delete Selected button

Opens the confirmation dialog where you choose a replacement value.

If you uncheck every box, the toolbar disappears automatically again.

5. Choose a Replacement Value and Confirm

When you click Delete Selected, the standard delete-confirmation dialog opens. This is the same dialog you already use when deleting a single value — but it comes pre-filled with all the values you ticked.

The dialog asks two things:

Field

Description

Example

Values to

delete

The list of values you selected. You can review them here, and remove any you didn't mean to include before confirming.

Larry , Joe ,

Suzy

Replace

with

The existing picklist value that should be assigned to any record that currently uses one of the values being deleted.

Unassigned

Steps inside the dialog:

1. Confirm the list of Values to delete is correct.

2. Pick a Replace with value from the dropdown.

3. Click Save (or Delete, depending on your theme labeling) to confirm.

The dialog closes, the selected rows disappear from the table, and you'll see a success message.

6. What Happens Behind the Scenes:

When you confirm a bulk delete, the CRM does all of the following — automatically, in one operation

Action

Result

Removes the selected values from the picklist field

They no longer appear in any form dropdown using this field.

Migrates existing records

Any record (Lead, Account, etc.) that currently uses a deleted value is updated to use your chosen Replace with value. No records are deleted, and no data is lost.

Cleans up role assignments

If the picklist is role-based, the deleted values are also removed from every role's assigned list.

Cleans up picklist

dependencies

If the deleted values were linked in a picklist dependency (parent/child dropdown rules), those dependency rules are cleaned up.

Updates the default value

Refreshes caches

If a deleted value happened to be the field's default, the default is reset.

The internal picklist cache is invalidated so all users see the updated list immediately.

Did this answer your question?