In this webinar, our experts showcase a variety of demo use cases of how different components of the...
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:
Before:
After:
Interested in this – let us know.
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'
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.
If I have someone interested - is this something that you are selling or sharing how you did it? Thanks!
All of our components are free to our clients, but we don't individually sell these small parts.