When This Happens
This occurs when:
A picklist field has dependencies configured (e.g., Unqualified Reason depends on Lead Status)
You add a new value to the dependent picklist
The picklist dependency configuration hasn't been updated to include the new value
How Picklist Dependencies Work
Picklist dependencies control the relationship between two fields. For example, if "Unqualified Reason" depends on "Lead Status", only specific unqualified reasons will show based on the selected lead status.
When you add a new picklist value, it must be mapped in the dependency configuration to determine when it should appear in the dropdown.
What To Do
If you add a new picklist value and it doesn't appear:
Contact your system administrator or Dazos support
Provide the field name and new value you added
The dependency configuration will need to be updated to include your new value
⚠️ Note: Only system administrators can update picklist dependencies through the Settings module.
Tips & Best Practices
💡 Tip: Before adding new picklist values to dependent fields, check if dependencies are configured and plan for the update process.
✅ Best Practice: Document your picklist dependencies so you know which configurations need updating when adding new values.
Related Resources
For assistance with picklist dependency updates, contact Dazos support with your specific field names and new values.