DocumentationAEMAEM Assets Tutorials

Cascading metadata cascading-metadata

Last update: September 1, 2026
  • Applies to:
  • Experience Manager 6.4
  • Experience Manager 6.5
  • Experience Manager as a Cloud Service

CREATED FOR:

  • Intermediate
  • User

Cascading field rules create contextual relationships between metadata fields: a field’s requirement, visibility, or list of choices can depend on the value of another field. This video shows an administrator apply these rules to a custom metadata schema.

https://video.tv.adobe.com/v/20702?quality=12&learn=on
https://video.tv.adobe.com/vc/20702/eng.json

There are three dynamic rule sets that can be enabled for a given metadata field:

  1. Requirement : a field can dynamically be marked as required to be based on the value of another dropdown field.

  2. Visibility : fields can always be visible or only visible based on the value of another dropdown field.

  3. Choices : (only applicable to dropdown fields) filter the choices shown to the user based on the currently selected value of another dropdown field.

recommendation-more-help
experience-manager-learn-help-assets