Configuring Different Default Views for Duplicated Tables in Dynamics 365 Model-driven App Sitemap/Navigation

 When configuring a model-driven app in Dynamics 365, it's common to need different default views for the same entity to suit various user needs. For example, if you add the "Contact" entity twice to the app's navigation panel, you can set different default views by varying the content type.