<p>The native <a href="https://craftcms.com/docs/4.x/entries-fields.html" rel="nofollow noreferrer">entries field</a> in Craft doesn't support this. The entries field always has a source and a target entry, and in the Control Panel, you only see the related entries in the source entry. For bidirectional relations that are also visible in the Control Panel, you can use the <a href="https://plugins.craftcms.com/reverserelations?craft4" rel="nofollow noreferrer">Reverse Relations plugin</a>.</p>
<p>However, you might not need this. Under the hood, all relations are stored in a junction table, and you can query for related entries regardless of direction:</p>
<pre class="lang-twig prettyprint-override"><code>{% set relatedArticles = craft.entries()
    .section('articles')
    .relatedTo({ element: entry, field: 'relatedArticles', })
    .all()
%}
</code></pre>
<p>This will give you a list of all articles that are related to the current <code>entry</code> through the <code>relatedArticles</code> field, regardless of which one is the target and source element. You only need the plugin above if you absolutely need those bidirectional relations to be visible in both entries in the Control Panel.</p>

CC BY-SA 4.0
2023-08-01T14:35:28.203Z
Whow ... this answer is gold worth ... thank you so much, Moritz!
Marc 
CC BY-SA 4.0
2023-08-01T13:55:00.767Z
2023-08-01T13:55:00.767Z
MoritzLost
<p>The solution from Moritz seems to work.</p>
<p>I suggest to set the <strong>Reverse Plugin Field</strong> to read-only.
This should reduce the complexibility for the editor in the control panel.</p>

CC BY-SA 4.0
2023-08-01T14:38:54.773Z
2023-08-01T14:38:54.773Z
Marc 
<p>Is ist possible to &quot;concatenate&quot; entries?</p>
<p>For example:</p>
<ul>
<li>You have five articles (A, B, C, D, E) ... might be a blog</li>
<li>Editing the article A: A is related to C and D</li>
<li>The relation should work bidirectional: Articels C and D know their relation to A automatically ... some kind of &quot;this article got a relationship from article A&quot;</li>
</ul>
<p>The idea behind: You have not to edit all three articles.</p>
<p>My question is concerning the control panel, not just the templates.</p>

<entries><control-panel><relationships>
control panel: bidirectional related entries // concatenate entries
# control panel: bidirectional related entries // concatenate entries

(Asked by: username_0 on 2023-08-01)

Is ist possible to "concatenate" entries?

For example:

* You have five articles (A, B, C, D, E) ... might be a blog
* Editing the article A: A is related to C and D
* The relation should work bidirectional: Articels C and D know their relation to A automatically ... some kind of "this article got a relationship from article A"

The idea behind: You have not to edit all three articles.

My question is concerning the control panel, not just the templates.

**Tags:** entries, control-panel, relationships


---

## 2 answers

### Answer by username_1 on 2023-08-01. Score: 2 | Accepted answer

The native entries field in Craft doesn't support this. The entries field always has a source and a target entry, and in the Control Panel, you only see the related entries in the source entry. For bidirectional relations that are also visible in the Control Panel, you can use the Reverse Relations plugin.
However, you might not need this. Under the hood, all relations are stored in a junction table, and you can query for related entries regardless of direction:
{% set relatedArticles = craft.entries()
    .section('articles')
    .relatedTo({ element: entry, field: 'relatedArticles', })
    .all()
%}

This will give you a list of all articles that are related to the current entry through the relatedArticles field, regardless of which one is the target and source element. You only need the plugin above if you absolutely need those bidirectional relations to be visible in both entries in the Control Panel.

> **Comments:**
> **username_0**: Whow ... this answer is gold worth ... thank you so much, Moritz!  

---

### Answer by username_0 on 2023-08-01. Score: 1

The solution from Moritz seems to work.

I suggest to set the **Reverse Plugin Field** to read-only.
This should reduce the complexibility for the editor in the control panel.


---

