Fix the UX of Entity Reference fields [#2116551]

Problem/Motivation [#1757452] added config entities back into the selection here, after this was deliberately taken out in [#1801304] taken out of the UI since the initial ER pach didn't support config entities. This leads to completely silly lists of possible things to reference like this: Here you have your "90% case" stuff (Content, Users, Files, etc.) buried hopelessly in amongst a bunch of "1% or less case" stuff like "Editor" and "Text format" and "Breakpoint group." This needs to be fixed, because it makes what's already a challenging field to use about 600x more difficult.

Prioritize 'add existing' in nested entity creation UX to prevent

8 - Entity Reference: Filter by an entity reference view not

Custom Action Invalid Argument Error : Entity Reference cannot

drupal - How can I limit an entity reference selection to a

Views relationships with multi-valued entity reference fields

Loading Dynamics CDM with Azure Data Factory (@entityReference

Solved: VISA: (Hex 0xBFFF0011) Insufficient location information

Fix the UX of Entity Reference fields [#2116551]

8 - View for Entity Reference reverse, backwards forwards - Drupal

AL0604: The identifier field name could not be found · Issue

Business central 18.4 - Metadata object missing for query

Libero Config Get File - Colaboratory

How to Enforce Selection of Published Contents in Entity Reference

8 - Entity reference view depending on other field - Drupal Answers