Skip to main content
Drupal is a registered trademark of Dries Buytaert
Release: OpenID Connect / OAuth client 3.0.0-alpha9 New alpha version released for module openid_connect (3.0.0-alpha9). Usage Milestone: Google Analytics Module google_analytics crossed 1,000 active installs. Release: Timelinr 1.0.1 Minor update available for module timelinr (1.0.1). Release: GraphQL Compose Codegen 1.1.2 Minor update available for module graphql_compose_codegen (1.1.2). Release: Mapy.com 1.1.3 Minor update available for module mapycom (1.1.3). Release: Ckeditor5 entity browser 3.0.3 Minor update available for module ckeditor5_entity_browser (3.0.3). Release: Ckeditor5 entity browser 3.0.1 Minor update available for module ckeditor5_entity_browser (3.0.1). Release: Ckeditor5 entity browser 3.0.2 Minor update available for module ckeditor5_entity_browser (3.0.2). Release: Teamleader Integration 4.0.2 Minor update available for module teamleader (4.0.2). Module Revived: Entityqueue Buttons 1.1.2 Module entityqueue_buttons updated after 8 months of inactivity (1.1.2).

Entity Reference Automation

14 sites Security covered Drupal 10–11
View on drupal.org

This module automatically fills in field data based on existing relationships between content entities. It aims to simplify content editing by pre-populating fields, allowing users to review changes in the browser before they are finalized. This helps ensure content is more organized and reduces manual duplication of information.

Entity reference simplifies content editing by auto filling field data based on relations when changes are made to a content entity. This takes concern away from worrying about assigning values on two fields, and means that content can be more organized. The auto fill of fields is handled in the browser, to allow the user to review the values before the change is made.

Example usage:

Case 1: ER Auto can be useful on complicated sites, where multiple taxonomy, entity references, or fields, are duplicated across entities. A site might use two taxonomies. One for access control. the other for filtering content in search and views. If the site usually attaches a set of access terms to a category, then this can be automated using ER Auto. Allowing a content editor only to be concerned with the topic of their new content, not who needs to be able to access it.

Case 2: A tech business, has a knowledge base. They have categories and tags for different topics. They might use ER Auto to associate a "end user" topic to "how to documentation" while other content, such as "API" or "Admin account" might be reserved for more technical users.

Setup

These are the steps to setup a basic reference automation. Use case: New issues should be automatically assigned to the project owner.

1) Field configuration:
- The project content type has an Entity Reference field `owner` that has a target type `user`.
- Similarly, the issue content type, has an Entity Reference field `assigned_to` that has a target type `user`.
- The issue content type also has a Entity Reference field `project` that has a target type `node`.
2) On the config page, for the `project` field, check `Enable Automation based on this field?
3) Select the `owner` field from the first multi select.
4) Select the `assigned_to` field on the second mutliselect.
5) save.

Now when setting the project for an issue, the assignee will be pre populated.

Depends on

Dependencies of the latest stable release

No dependencies recorded for this project.

Required by

Tracked projects that depend on this one

No tracked projects depend on this one yet.

Activity

Tracked releases
5
Tracked since
Oct 2025
Latest release
10 months ago
Releases (12 mo)
5 ▲ from 0
Maintenance
Slowing

Release Timeline

Releases

Version Type Core Release date
2.1.1 Stable 10–11 Oct 16, 2025
2.1.0 Stable 10–11 Oct 13, 2025
2.0.0 Stable 10–11 Oct 13, 2025
2.x-dev Dev 10–11 Oct 13, 2025
8.x-1.1 Stable 8–11 Oct 8, 2025