web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Setting a Default View...
Microsoft Dynamics CRM (Archived)

Setting a Default View resulted in two default views

(0) ShareShare
ReportReport
Posted on by Community Member

I have a customer for whom I had created a custom view of the user entity, and set that view as the default view.  However, after a recent update, the default view switched back to "Enabled Users".  Now if I set another view as the default, both views show as being the default public view, and CRM treats the "Enabled Users" view as the default.  This creates an extra step for them on the Service Calendar where a user cannot set a personal default view.

I have considered trying to edit the "Enabled Users" view, but because they show disabled users in their default view (for scheduling), this would be confusing for other people and the "Enabled Users" view may also get overridden at some point in a future update.  I would prefer to find a way to set the custom view back to default if anyone has any ideas.

Thanks,

Jeff

*This post is locked for comments

  • SrinivasCh Profile Picture
    SrinivasCh on at
    RE: Setting a Default View resulted in two default views

    I have created new view and set that as default.

    It made 'enabled users' as 'public view' and my custom view 'customized default view' as default public view.

    May you creating a public view and set it as 'default view'.

    3750.Capture1.JPG

    I hope i have answered your question to some extent. Hope this helps!!

  • Suggested answer
    Daniel Wikell Profile Picture
    Daniel Wikell on at
    RE: Setting a Default View resulted in two default views

    An annoying bug, since setting another view to default will look for 1 view to remove default from.

    What you can do is add the user entity and all view assests of it to a new solution, export the solution and extract the customizations.xml file from the solution zip. Look for the IsDefault attribute for the views and set them to false on all but one view. Re-add the customizations-xml to the zip file and import it again into your organization. This should make it go back to only having 1 default.

  • Suggested answer
    Abhishek.D Profile Picture
    Abhishek.D on at
    RE: Setting a Default View resulted in two default views

    Because of the new update this issue came into the picture that for all the out-of-box views you can change the default views but if you try to make a custom view as default, it will make it default but the already default view will remain default with higher priority.

    So what you can do is check if there is any not important or not in use out-of-box view is there-

    1. Select that view and make it default.

    2. Make your custom view as Default.

       Now you have 2 default views.

    3. Now go to the model driven app and uncheck the out-of-box view that you made default in step 1 and if your

       custom view is not checked then check it and publish the changes.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans