Acquia DAM (Widen)
What are dependent metadata fields?
If your metadata model requires conditional or single-selection fields, consider the following design patterns:
Invert the dependency structure: Make the single-select dropdown the parent field, and assign supported dependent fields (such as a text field, numeric field, or palette) as children under specific list values.
Use a palette or checkbox group: Configure a multi-select palette or checkbox group as the dependent child field, and use governance guidelines or asset review workflows if single-value entry is required.
Use a binary trigger: Use a dropdown parent with options such as Yes and No to conditionally display a single checkbox or text field for specific input (such as licensing restrictions).
A parent field can have multiple dependent fields:
Product catalog: A parent dropdown field named Product Brand Name can control four child dependent fields: Product Description, Product Type, Manufacturer, and Product Size.
Asset classification: If you select Photography in the Asset Type parent field, a Photo Type dependent field displays. If you select a value other than Photography, a different dependent field displays.
Rights management and licensing: A parent dropdown field can specify whether licensing restrictions apply. If Yes is selected, a dependent field displays to allow users to specify terms, expiration dates, or vendor rights.
To create parent and dependent metadata fields:
Access the Admin app.
In the navigation pane, select Metadata types under Search settings.
Select a metadata type, or select Edit Fields to add a dependent field to an existing metadata field.
Select Create field, enter a field name and key, and then select the Dropdown list option for the field type.
Under Does this field have dependencies?, select Yes.
Select Edit by List Values.
Enter a value and select Add. The values display as you add them. You can sort them alphabetically or drag and drop them to reorder.
After adding all values, select Done.
After creating the list values, assign previously created metadata fields as dependent fields:
Select Assign Dependencies for the newly created values. A list of created metadata fields and their dependency status displays.
Select the fields you want to configure as dependent fields for the values you created.
For example, for the Photo value, select Department and Product Line as dependent fields. Users must complete these fields when Photo is selected in the Asset Type field.
If you require additional values (such as Region or Launch Year), select Not Selected to toggle the status to Selected.
You can refine searches by dependent metadata fields if you enable the Show Dependent Metadata Fields in Refine Search feature on the Features page.
You must select Yes in the Search Filter option for a metadata type for dependent fields to display in refined searches. Dependent fields always display when refining searches, even if the parent field is not configured to display.
If a configured dependent field (such as Asset Language or Licensing Terms) does not display on an asset edit form, upload modal, or search filter, review the following checklist:
Verify exact parent value selection: Dependent fields display only when the exact parent trigger value is selected. Verify that the parent field value matches the rule configured under Assign Dependencies.
Check field permissions and role access: Ensure that the user role has permission to access both the parent field and the dependent child field. If a user lacks permission to access the dependent field, it does not display even when the parent condition is met.
Verify form and metadata type layout:
Ensure both the parent and dependent fields are included in the active metadata type applied to the asset.
In the metadata form layout, place the parent field earlier in the display order than the dependent field so users encounter and select the trigger before completing dependent details.
Check asset history and population: On existing assets created before the dependency rule was introduced, the child field remains hidden until the parent field is populated or re-saved with the trigger value.
Verify upload and edit template scope: If using custom upload profiles or specific edit templates, ensure that the dependent field has not been excluded or hidden from that template.
Review parent value modifications: If a parent list value was renamed or re-created, re-access the Assign Dependencies screen to confirm that the dependency mapping is still attached to the updated value.
Clear cache and refresh: After updating metadata configurations in the Admin app, log out or refresh the browser to clear cached form schemas.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Acquia DAM (Widen)