Overview
Before you begin, make sure you have:
Administrator access to CRM Settings
An existing field dependency configured for a field that is hidden by default
Knowledge of all possible values for the source (controlling) field — including the empty/blank state
The Problem This Solves
If your target fields are hidden by default and you have built a dependency to show them under a specific condition, you may notice that after the field shows correctly, it fails to re-hide when the source field is changed back to a different value.
This happens because the dependency logic is built only around the show condition, so when the source value changes away from that condition, the dependency does not retrigger to hide the fields again.
Steps
Identify all possible values of your source field. List every value the source picklist can hold — including the blank/empty state. For example, if a field can be empty, Medical, or Behavioral, you have three states to account for.
Determine which values should keep the target fields hidden. Since the target fields are hidden by default, focus on the conditions that should maintain that hidden state rather than only on the condition that shows them. In the example above, if the fields should only appear when the value is Behavioral, then the hide conditions are: empty and Medical.
Open your field dependency. Navigate to Settings → CRM Settings → Module Management → Module Layouts & Fields, select your module, and open the Field Dependencies tab. Click into the existing dependency you need to fix.
Restructure the dependency logic to cover all hide states. Instead of building the rule around only the show condition, add explicit conditions for each value that should result in the fields remaining hidden. For example:
Condition: source field is empty → Action: Hide target fields
Condition: source field is Medical → Action: Hide target fields
Condition: source field is Behavioral → Action: Show target fields
Save the dependency. Click Save after updating all conditions and their corresponding actions.
Test all value states. On a record, cycle through each possible value of the source field — including clearing it to blank — and confirm that the target fields show and hide correctly in every state.
Result
After restructuring the dependency to explicitly cover all states that should result in hidden fields, the dependency will retrigger correctly whenever the source field value changes. The target fields will show and re-hide as expected across all value transitions.
Important Notes
Why this works: When target fields are hidden by default, the dependency needs a condition to actively re-apply the hide action whenever the source value changes to a non-showing state. Without explicit hide conditions for those states, the dependency has nothing to retrigger, and the fields remain visible after they are shown once.
Cover all values: Make sure your hide conditions account for every value that should not show the target fields — including the empty/blank state. Missing even one value can cause the re-hiding to fail for that specific transition.
💡 Tip: After saving your updated dependency, clear your browser cache and test each picklist value individually to confirm the correct fields are showing and hiding as expected in all scenarios.
Still Need Help?
If your fields are still not re-hiding correctly after restructuring the dependency logic, contact Dazos Support with the following information:
The module and field dependency name
The source field name and all its possible values
A description of which value transitions are not behaving as expected
Screenshots of your current dependency configuration