Symptom/Error
Cause
This issue occurs when a picklist has dependency mapping configured. Even though new values are added to the picklist, they need to be manually mapped to the parent field in the dependency settings before they become available for selection. The values exist but are not visible because they haven't been included in the dependency mapping.
Solution
This issue requires administrative access to update dependency mappings. Follow these steps:
Contact Support: Reach out to Dazos Support to update the picklist dependency mapping for your new values. This requires administrative privileges that are not available to standard users.
Provide Details: When contacting support, include:
The specific picklist field name (e.g., "Unqualified Reason")
The new values that aren't appearing
The module where the picklist is located
Wait for Confirmation: Support will update the dependency mapping to include your new values and confirm when the changes are complete.
Refresh and Test: Once Support confirms the mapping has been updated:
Refresh your browser completely
Clear your browser cache if the values still don't appear
Test the picklist dropdown to verify new values are now visible
Verification
After the dependency mapping is updated:
New picklist values will appear in dropdown menus when editing records
Users can successfully select and save the new values
Values will be available across all forms where the picklist is used
Escalation
Contact Dazos Support if:
New picklist values don't appear after a browser refresh
You need dependency mappings updated for multiple picklist fields
The issue affects critical business processes
⚠️ Important: This troubleshooting applies specifically to picklists with dependency configurations. Simple picklists without dependencies should show new values immediately after being added.
Related Resources
Setting Up Picklist Dependencies in Dazos (CRM)
How to Map Picklist Values in Dazos CRM
How to Save Picklist Values After Adding Them (CRM)