Contents
1. Before You Start
2. Open Field Dependencies
3. Add a File-Upload Field as a Target
4. How It Behaves on Records
5. Frequently Asked Questions
1. Before You Start
You will need:
Administrator access to CRM Settings
A module that already has a file-upload field (created in the Layout Editor with the "Files Upload" field type)
A source field (for example a picklist) whose value should control when the upload field appears
Access requirements: Any admin who can manage Module Layouts & Fields can configure this. No additional feature flag or instance setting is required — the capability is available on all modules that support Field Dependencies.
If you don't see the Field Dependencies tab for your module, contact Dazos support to confirm the module supports it on your instance.
2. Open Field Dependencies
From the CRM, navigate to Settings → CRM Settings → Module Management → Module Layouts & Fields.
1. Select your module (for example Intake Opportunities).
2. Open the Field Dependencies tab.
3. Click into an existing dependency, or create a new one and give it a title.
4. Build your condition as usual — for example, Level of Care equals Detox .
3. Add a File-Upload Field as a Target
In the Target Field & Action section, click Add Target and open the target list. Your file-upload fields now appear alongside the other fields.
Control | Purpose |
Target field | Pick your file-upload field (e.g. New Insurance Upload ) |
Action | Choose Hide or Show |
Add Target | Add more fields to the same rule if needed |
1. Select the file-upload field as the target.
2. Choose Hide or Show.
3. Click Save.
Tip: File-upload targets offer only Hide and Show. The Required and Editable actions are not available for them — an upload area has no typed value to require or lock, so those actions would have no effect.
4. How It Behaves on Records
Once saved, the rule applies automatically wherever the record is edited:
Where | Behavior |
Edit page | Changing the source field instantly shows or hides the upload area — no save needed to see the effect |
Create page | The rule is evaluated as soon as you fill in the source field |
Mass Edit | The same show/hide behavior applies in the mass-edit window |
When the upload field is hidden, its space on the form is kept blank so the other questions don't shift around (the same layout-stable behavior used for all field dependencies).
Important: Hiding an upload field is a display convenience, not a security control. Files that were already uploaded remain stored with the record and are still visible in other areas that list the record's documents.
5. Frequently Asked Questions
Q: Why don't I see Required or Editable for my file-upload target? Those actions only make sense for typed inputs (text, picklists, dates). An upload area can't be "required" through form validation or set read-only the same way, so only Hide and Show are offered.
Q: Can I use the file-upload field as the condition (the "if" part) of a dependency? No. Conditions compare values — an upload field has no single value to compare. Use it only as a target.
Q: If the field is hidden and the user had already uploaded files, are they deleted? No. Uploaded files stay attached to the record. Hiding only removes the upload area from view while the condition applies.
Q: Does this work on every module? Yes — any module that supports Field Dependencies now lists its file-upload fields as targets, on every instance.
Q: We reported this for one specific field. Do we need to reconfigure anything? No. Open your dependency, click Add Target, and the field simply appears in the list now. Existing rules are untouched.
Q: Does the rule affect PDFs generated from the record? No. File-upload fields are not printed in record PDFs, so PDF output is unchanged.
Need Help?
If you run into issues:
1. Confirm the field's type is "Files Upload" in the Layout Editor and that the field is active.
2. Re-open the dependency and verify the target row shows your upload field with Hide or Show selected, then re-save.
3. Contact Dazos support with your module name and dependency title, and reference CRM-3463.