How to get referring items from a Entityreference field in the opposing item list? (back reference) Using an Entityreference field in a content type A makes it possible to reference multiple items from another content type B to it. On node teaser pages or any other Views lists you can list them additionally on each row of content item from the content type A as a sub-list of referenced items. But how can I list the reference sources the other way around automatically without using another Entityreference field on the content type B (needless double-edit)?

Example: A car (content type A) has been repaired in 3 different car service stations (content type B). So the content type "car" gets a Entityreference field to add them (items from B). When I build a list of service stations (B), I would like to see a list of the cars (A) being repared in them automatically without an additional back reference field or additional modules like CER, making things needlessly complicated in the database.



NOTE: Basically it's the behaviour we would expect from Taxonomy terms, which are also Entityreferences in Drupal 8, but they seem to have some more build in functionality to work from both sides in item lists.
At the moment I only see 2 (edit: 3) options to solve the backreferencing issue without creating SQL request duplicates:


Using Views Field View for nesting a list of type A nodes referencing node type B via contextual filters in the second view to filter for each items nid (possible performance issue).
Syncing 2 Entityreference fields from both content types and maybe automate them with Rules and using the second Entityreference field for the back reference list in Views.
Using the CER module (I know you said no but), I think after testing that this module is the best option at the moment if you know that you want this connection synced "fix" and not individually changed.


First would have a huge performance impact if the lists and nested lists are long. And the caching modules required to compensate it are not ready yet for D8.

Second can have other issues sinces Rules not always work flawlessly and I am not 100% sure if Rules supports the needed triggers for this approach.

EDIT: Third is my recommendation. After testing around I was quite impressed about its simpleness and working warranty. It's not as flexible as using rules, but as I sad, rules is a story of ots own. So maybe you give it another try (CER).