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.

360 Core (Client Center, E-Journal Portal): Release Notes and

Add Entity reference fields like: User reference, Content

Remove Taxonomy term reference field in favor of Entity reference

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

No unique index found for the referenced field of the primary

Fix the UX of Entity Reference fields [#2116551]

Lookup] Selected record tag is emtpy or shows No name

Deleting References

KA-01213 · Customer Self-Service

CRM (on-prem) – Entity reference cannot have Id and Key Attributes