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.

Loading Dynamics CDM with Azure Data Factory (@entityReference

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

Add Entity reference field [#1801304]

KA-01213 · Customer Self-Service

Add Entity reference fields like: User reference, Content

c# - System.Data.Entity.Infrastructure

Remove Taxonomy term reference field in favor of Entity reference

Add Entity reference fields like: User reference, Content

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

BMC Helix Remedyforce: “ENTITY_IS_LOCKED, This record is locked

no unique index found for the referenced field of a primary table

Fix the UX of Entity Reference fields [#2116551]