Hello fellow Microsoft CRM 4.0’ers – today’s blog entry involves an issue that at least 3 implementations that I’m aware of are suffering. This issue sometimes appears when you import customizations and subsequently attempt to change the default public view for that entity.
In this scenario, I’ve renamed the “Accounts” entity to “Company” (a common customization) and according to the business requirements I attempted to change the default public view to “Active Companies.”
When this is completed we see two default public views for this entity:
There are a few things you can do to correct this situation including going into the xml for the entity or perhaps taking a trip into the metadata in the database, but to stay within supported territory this is an easy fix.
First, create a new view:
And name it ‘temp.’
Next – assign it a filter criteria, it matters little what it is…
…and you should have something that looks like this:
Next – set your newly created view as the default view for that entity. Notice that you STILL have two default public views for that entity:
Now you must publish the entity you’re working with:
Now, go into your new temp view to the “More Actions” menu and delete the view.
Finally, (very important) Publish your entity.
Now you should be able to go into your entity and set default views without ending up with multiple default views!
Microsoft CRM Consultant
Unitek Microsoft CRM Services