Custom Object & Company Fields: Option Deletion Now Live

TL;DR

Options can now be deleted from Custom Object and Company fields. Existing records retain deleted values; future selections will not show them.

Who this affects

This update affects any agency or SaaS entrepreneur using Custom Objects or Custom Fields within Companies. If you have been restricted by undeletable options in your custom fields, this applies to you. If you do not use these features, you can ignore this update.

What changed

HighLevel has implemented the ability to delete options from several custom field types. Specifically, options can now be removed from Dropdown, Multi-select, Radio, and Checkbox fields when configured for Custom Objects and Companies.

Key points regarding this change:

• Options are removed from future selection, meaning they will not appear as choices for new or edited records.
• If an option that is deleted was already in use on existing records, those records will retain the value. The deletion does not retroactively remove data from existing entries.
• Before confirming a deletion, the system will show how many records currently use that specific option. This provides context for the impact of the deletion.
• Existing filters, Smart Lists, and workflows that reference these deleted options will continue to function. The system maintains compatibility for these operations.

HighLevel has not confirmed the rollout status, who is affected by this specific change, or if it replaces existing functionality or has any limits or plan gating.

Where to find it

This functionality is located within HighLevel's settings, specifically by navigating to Settings → Custom Fields. From there, you would edit the relevant Custom Object or Company field to access the option deletion feature.

How agencies will use this

Agencies often evolve their data structures as client needs change, or they might make errors during initial setup. For instance, an agency setting up a Custom Object for 'Project Status' might have initially included 'On Hold - Client Side' and 'On Hold - Agency Side' as dropdown options. Over time, they might simplify this to a single 'On Hold' option. Previously, the redundant options would clutter the dropdown, making it harder for users to select the correct status. Now, the agency can navigate to Settings → Custom Fields, find their 'Project Status' field within the Custom Object, and delete the specific 'On Hold - Client Side' and 'On Hold - Agency Side' options. Before deletion, the system will show if any projects are currently marked with these specific statuses. If projects exist, those project records will retain their 'On Hold - Client Side' or 'On Hold - Agency Side' status, while new projects or project updates will only see the consolidated 'On Hold' option, streamlining data entry.

Our take

This is a standard quality-of-life update. It addresses a common frustration when managing custom fields: the inability to clean up outdated or incorrectly added options without recreating the entire field. While not a groundbreaking feature, it tidies up the HighLevel experience for anyone heavily relying on Custom Objects and Company fields. It's a small but welcome fix for data hygiene.