Skip to main content

Data Fields: Troubleshooting Guide

This guide outlines frequent scenarios, limitations, and troubleshooting steps for Pipedrive Custom Fields.

Written by Irina

1. Field Creation, Management & Forms

Creating New Custom Fields (Not Grouped)

From the Detail View of items you can reorder shown there, however it's only possible to create a standalone custom field for deals that isn't bunched into a specific field group, navigate to Settings > Company settings > Data fields.

When creating the custom field you can select if the field stays "ungrouped" or organize it to a fields group.

Custom Fields in Web Forms

  • Scenario: User wants to create custom fields directly inside a web form.

  • Solution: Custom fields can't be created from within the web form builder. They must first be created directly in the Data Fields Settings before they can be pulled into a web form.

Setting Up Phone Numbers for Account Users

  • Scenario: Setting up or modifying a phone number for an account user (not a contact).

  • Solution: This can't be done by account admins or users. This request must be handled by Support Agents.

Reverting Field Changes

  • Scenario: User wants to undo a recent change made to a custom field's configuration.

  • Solution: There is no automatic "revert" or version history tool for custom fields. This request must be handled by Support Agents.

Managing Lost Reasons

To customize or add options for why deals are lost, direct users to the Lost Reasons Settings.

2. Visibility & Display Logic

Hiding Fields vs. Pipeline View

Deal and Lead custom fields allow you to adjust visibility settings based on specific pipelines.

The Pipeline Visibility Logic:

  • Field has data + Hidden in pipeline: The field will move and show under the "Hidden" section of the deal detail view so data isn't lost.

  • Field has NO data + Hidden in pipeline: The field will be completely invisible on the deal (it won't even show in the hidden section).

Separating Deal Fields from Lead Views

  • Scenario: User wants to see fields in Deals but hide them in Leads because it confuses sales reps.

  • Solution: Because Deal and Lead fields are structurally grouped together in Pipedrive, there is no way to hide Deal-type fields specifically from the Lead view.

Weighted Value in Details View

  • Scenario: User cannot find the "weighted value" in the deal details view.

  • Solution: This is expected behavior. Weighted value cannot be displayed in the deal details view; it is only visible in the List View.

Missing Data Fields Sidebar

  • Scenario: User is unable to see the "Data Fields" on the side of their screen.

  • Solution: The sidebar was likely accidentally collapsed. Have the user check the edge of the screen to expand the sidebar.

Dropdown Menu Stays Open

  • Scenario: After selecting an option, the dropdown menu for the custom field refuses to close.

  • Solution: Check the field type. It is likely a multiple-option field rather than a single-option dropdown. Multiple-option fields stay open intentionally to let users select more than one answer.

Numbers (IDs) Showing Instead of Names

  • Scenario: Custom field options or names are showing up as raw database IDs.

  • Solution: This is not expected behavior. Instruct the user to clear their browser cache and cookies, then refresh the page. If it still happens even after testing with a incognito window, reach out to Support Agents.

3. Data Entry & Editing Behavior

Greyed Out / Uneditable Fields in "Add Deal/Lead" View

  • Scenario: User cannot edit specific contact fields when creating a new lead or deal.

  • Solution: This happens because an existing contact has the information added already. Because that information belongs directly to the established contact profile, Pipedrive greys it out to prevent accidental overwrites.

  • Note: These fields are only editable during the "Add" view if you are creating a brand new contact at the same time. To change it for an existing contact, edit their profile directly.

Bypassing Required Fields

  • Scenario: A user successfully created a deal manually without filling out a field that was supposed to be required.

  • Solution: Check the field's configuration under Data Fields settings. The field was likely set to "Important" rather than "Mandatory". Important fields prompt the user but do not strictly block deal creation.

Duplicated Country Fields

  • Scenario: User sees two different "Country" fields on a record and can't locate one of them.

  • Solution: This is expected. One is a standalone Country custom field created by the user, and the other is an automatic Country sub-field tied to a main Address field.

Formula Fields

  • Scenario: User is looking to have a Formula Field as required.

  • Solution: It's not possible to mark Formula Fields as required or important as formula fields are calculated and filled automatically once all input fields in the formula have values.

How Address Sub-Fields Work

Whenever a field with the type "Address" is created, Pipedrive automatically generates hidden sub-fields (like City, State, Country).

  • When an address is typed in, geolocation automatically identifies and populates these sub-fields.

  • They do not show up under the "Data Fields" settings tab.

  • They cannot be edited manually; they are strictly dependent on the main Address field.

4. Errors, Automations, & Imports

Automation Error: "Review and remove the missing fields..."

  • Scenario: User can't activate an automation and gets an error message pointing to missing fields.

  • Solution: This occurs when an automation references a custom field that has been deleted or modified. The user needs to check if the field still exists in their data fields settings and update the automation workflow accordingly.

Missing Custom Fields During Data Import

  • Scenario: User can't find their custom fields when trying to map columns during an import.

  • Solution: Pipedrive attempts automatic mapping first, but unmatched fields must be mapped manually. Tell the user to click the icons individually, scroll through the list, or type the exact name of the custom field to map it properly.

Mandatory Country Code for Scheduler Links

  • Scenario: User needs to force invitees to input a country code on Scheduler links.

  • Solution: There isn't a native "mandatory country code" toggle for the phone field in Scheduler. As a workaround, create a new custom text field specifically named "Country Code" and add this custom field directly to the Scheduler/web form setup.

Did this answer your question?