Registry data source

The registry data source supplies a list of definition providers of a given registry specified by the registry type. It is only used in column filters in the Definitions app (see Searching and filtering definitions). By default, it does not provide any component implementation itself other than the one required by select fields.

The registry data source is part of the Magnolia 6 UI framework. The fully qualified class name is

If you work with the Magnolia 5 UI framework, see Content connector instead.

Example definition

  name: registry-contents
  type: dialogs

List of properties

Property Description



Fully qualified name of the definition class.




Type of registry. Examples include apps, dialogs and templates.


optional, default is registry-contents

Name of the data source.

Data source components

Module component mappings can be defined in the context of the current data source (a component section should have an id in the form of <id>datasource-<ds-name></id>, where <ds-name> is configured in the definition).

Type Implementation Description


Provides delegates required by select fields.

Component mappings in module descriptor

DX Core



This widget lets you know where you are on the docs site.

You are currently perusing through the DX Core docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules
6.3 beta

Magnolia 6.3 beta

Magnolia 6.3 is in beta. We are updating docs based on development and feedback. Consider the 6.3 docs currently in a state of progress and not final.

We are working on some 6.3-beta known issues during this phase.