This limitation occurs when you're trying to:

The reference field will not appear in the "Target Field & Action" dropdown when creating field dependencies.
​

Reference fields create links between different modules in the system. The field dependency builder is designed to work with fields within the same module and cannot target these cross-module field relationships.
​

Standard field types like text, date, picklist, and number fields work normally with dependencies, but any field that references another module will be unavailable as a target.
​

When you need to make a reference field required or control its behavior, you have these options:
​

Make the field mandatory at the module level in Fields & Layouts. This ensures the field is always required regardless of other field values.
​

Create the dependency at the Account level instead of the Intake Opportunity level. Account data typically carries over to Intake Opportunities when records are created, so this can provide similar functionality.
​

Use workflow automation to enforce field requirements or send notifications when reference fields need attention based on other field changes.
​

⚠️ Note: This limitation applies to all reference fields across all modules, not just specific fields like Referral Source.
​

💡 Tip: When planning field dependencies, identify which fields are reference fields early in your setup to avoid configuration issues.
​

✅ Best Practice: Consider using Account-level dependencies when possible, as they often provide the same business logic while working within system limitations.
​

Understanding the Different Types of Field Dependencies in Dazos

How to Create Reference Fields in the VOB (CRM)

Troubleshooting Reference Fields Causing Required Validation in Quick Create