Fix the UX of Entity Reference fields [#2116551]

Por um escritor misterioso
Last updated 16 junho 2024
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.
Fix the UX of Entity Reference fields [#2116551]
AL0604: The identifier field name could not be found · Issue
Fix the UX of Entity Reference fields [#2116551]
entities - How to use the Render Views filters as select list
Fix the UX of Entity Reference fields [#2116551]
Views relationships with multi-valued entity reference fields
Fix the UX of Entity Reference fields [#2116551]
Add Entity reference field [#1801304]
Fix the UX of Entity Reference fields [#2116551]
entities - How to use the Render Views filters as select list
Fix the UX of Entity Reference fields [#2116551]
Entity Reference Referential Integrity
Fix the UX of Entity Reference fields [#2116551]
Entity Reference Views
Fix the UX of Entity Reference fields [#2116551]
c# - System.Data.Entity.Infrastructure
Fix the UX of Entity Reference fields [#2116551]
Business central 18.4 - Metadata object missing for query
Fix the UX of Entity Reference fields [#2116551]
EntityAutocomplete not working with Views entity reference method
Fix the UX of Entity Reference fields [#2116551]
Keyword-based faceted search interface for knowledge graph

© 2014-2024 dakarshop.net. All rights reserved.