To improve usability and consistency in model-driven apps, it would be beneficial to enhance the navigation behavior of lookup columns when grouping is applied in views.
Currently, when users apply grouping in a view, lookup columns are no longer clickable for navigation, even when those columns are not used as the grouping criteria. This creates an inconsistent experience compared to non-grouped views, where lookup columns allow direct navigation to related records.
This limitation introduces challenges in real-world scenarios where users rely on grouping to better organize and analyze data, while still needing access to related records. As a result, users are forced to remove grouping or perform additional searches, which increases complexity in their workflow.
By improving this behavior, users would be able to maintain grouped views while still navigating to related records efficiently. This would help streamline daily operations and provide a more consistent and intuitive user experience across different view states.
Comments
Good idea, please implement this Idea in the future Dataverse version, this is really needed.
Category: Unified Experience: Search, navigation and performance
This idea is really practical and good for user experience. Please consider implementing it.
Category: Unified Experience: Search, navigation and performance
This highlights an inconsistency in model-driven app behavior where lookup navigation is unintentionally restricted when grouping is applied. Allowing lookup columns to remain clickable, even in grouped views and would significantly improve usability by enabling users to organize data without losing quick access to related records. This enhancement would create a more seamless and intuitive experience across different view configurations.
Category: Unified Experience: Search, navigation and performance