Types of Dependencies
Field Dependencies (Same Module)
Field Dependencies control field behavior within the same module. When one field's value changes, it can show/hide, require, or modify other fields in that same record. Field dependencies within the same module in Dazos are located in a tab in the Layout Editor (Module Layout and Fields) and provide our extremely flexible Conditions system, which allows you to get fully granular with your dependencies.
Examples:
Selecting "Alumni Team" on the Lead Source field on an Intake Opportunity might trigger the hidden "Referring Alumni Rep" field to become visible and required.
The "Last Suicide Attempt" field in the PAA is hidden by default. A field dependency will enable it and make it required when the field "Have you ever attempted to commit suicide?" Is set to Yes.
Related Module Dependencies (Cross-Module Logic)
Related Module Dependencies trigger actions across different linked modules. Changes in one module can automatically affect field behavior in a related module.
Example: When you change the "Sales Stage" in an "Intake Opportunity" to "Referring Out," it can automatically make the "Referral Stage" field required in the linked "Outbound Referral" module.
Picklist Dependencies
Picklist Dependencies show or hide specific picklist values based on selections in other picklist fields. This creates cascading dropdown menus where available options change dynamically.
Example: Selecting "California" in a "State" field might show only California cities in a dependent "City" picklist field.
When to Use Each Type
Field Dependencies: Use when you need to control field visibility, requirements, or behavior within a single module
Related Module Dependencies: Use when you need changes in one module to trigger field behavior in linked modules
Picklist Dependencies: Use when you want dropdown options to change based on other dropdown selections
Key Considerations
Performance: Avoid creating unnecessary dependencies as they can impact system performance, especially with Related Module Dependencies.
Planning: Map out your workflow logic before setting up dependencies to ensure they work together effectively.
Related Resources
Module Management Settings
Field Configuration Guides
CRM Settings Overview