Drupal is a registered trademark of Dries Buytaert
drupal 11.3.7 Update released for Drupal core (11.3.7)! drupal 11.2.11 Update released for Drupal core (11.2.11)! drupal 10.6.7 Update released for Drupal core (10.6.7)! drupal 10.5.9 Update released for Drupal core (10.5.9)! cms 2.1.1 Update released for Drupal core (2.1.1)! drupal 11.3.6 Update released for Drupal core (11.3.6)! drupal 10.6.6 Update released for Drupal core (10.6.6)! cms 2.1.0 Update released for Drupal core (2.1.0)! bootstrap 8.x-3.40 Minor update available for theme bootstrap (8.x-3.40). menu_link_attributes 8.x-1.7 Minor update available for module menu_link_attributes (8.x-1.7). eca 3.1.1 Minor update available for module eca (3.1.1). layout_paragraphs 2.1.3 Minor update available for module layout_paragraphs (2.1.3). ai 1.3.3 Minor update available for module ai (1.3.3). ai 1.2.14 Minor update available for module ai (1.2.14). node_revision_delete 2.0.3 Minor update available for module node_revision_delete (2.0.3). moderated_content_bulk_publish 2.0.52 Minor update available for module moderated_content_bulk_publish (2.0.52). klaro 3.0.10 Minor update available for module klaro (3.0.10). klaro 3.0.9 Minor update available for module klaro (3.0.9). layout_paragraphs 2.1.2 Minor update available for module layout_paragraphs (2.1.2). geofield_map 11.1.8 Minor update available for module geofield_map (11.1.8).

er_auto

17 sites Security covered
View on drupal.org

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.

Activity

Total releases
5
First release
Oct 2025
Latest release
6 months ago
Release cadence
2 days
Stability
80% stable

Release Timeline

Releases

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