Looking for PowerObjects? Don’t worry, you’re in the right place! We’ve been part of HCL for several years, and we’ve now taken the final step in our acquisition journey: moving our website to the HCL domain. Nothing else is changing – we are still fanatically focused on Microsoft Business Applications!

PowerObjects Blog 

for Microsoft Business Applications

CRM 4 - Hiding System Views

Post Author: Joe D365 |

Out of the box system views are not configurable. This means that we can't modify the search criteria and can't delete these views. However, via a plug-in we can control whether or not the end user sees these views. This is done by writing a plug-in against the "Retrieve Multiple" message on the "Saved Query" entity. In just a couple dozen lines you can write this plug-in and compare the View Name to see if it is one of the views to remove.

In order to make this 'configurable', we have created such a plug-in that simply looks at the view name. Any view with the prefix of 'To Be Removed' is removed from the list of views.

For example, to hide the 'Accounts: No Campaign Activities in Last 3 months', rename this view and add prefix of 'To Be Removed'

We looking at the list of views, this is then removed:



Interested in this – let us know.

By Joe D365
Joe D365 is a Microsoft Dynamics 365 superhero who runs on pure Dynamics adrenaline. As the face of PowerObjects, Joe D365’s mission is to reveal innovative ways to use Dynamics 365 and bring the application to more businesses and organizations around the world.

4 comments on “CRM 4 - Hiding System Views”

  1. I really like this solution, it keeps it simple, no config files or data, you just add the magic prefix.

    I think this would also work really well for showing and hiding views depending on the users BU or Team membership, I'm going to take this further next time I get an opportunity with a client. For example to show a view for only one BU:

    '[BUShow=Marketing]Accounts: No Campaign Activities in Last 3 months'

    1. Thanks Simon. Yeah - we have a similar idea on the drawing board. Our idea is to extend a custom entity to allow end users to pick and choose their default view per entity. So now which ever view you like best you can set as your default.

  2. If I have someone interested - is this something that you are selling or sharing how you did it? Thanks!

PowerObjects Recommends