Hide dynamic filter results in list filter

[felladin]

I am looking for a way to either entirely hide the dynamic filter result or to show the label of the dynamic filter instead of the result in a list filter.

I have created a module that among other conditions use a dynamic filter on one of the fields. It works as it should, but I want to hide it from the end users, without removing filters.

The reason I want to remove it is mainly because it shows a lot of results, making the page a huge text-blob, but also because the information is irrelevant for the users.

With regards

Anton Vettefyr

[Raju Koyagura]

Try using "Omit filter" option in the list controls, if it is not visible on form add using form layout. However make sure apply condition in which view you want to hide this filters or which users (may be specific roles) and also keep it in mind if you hide the filter search functionality also disabled on the list.

If you want to hide filter to all use "Omit filter" else use "Omit filter condition" write your own conditions.

[Gaurav Bajaj]

Hi Anton,

First, you can try adding roles to the dynamic filter option. If thats what you are not looking for, then

can try it by writing a before query BR to restrict it for end users.

This would let the module work and not display the filter option to end user.

Thanks

Gaurav

[Jaspal Singh]

Hi Anton,

You may find link Hide filters in related list & Hide filter from Related list Edit button helpful.

[felladin]

Hello,

Thank you for your replies, but as stated, all I want to hide is the specific Dynamic Filter result for its field.

We still need the filter options to be there, as they are used by the technicians.

The best solution would be a way to display the Dynamic Filter Label in the filter list, instead of its results. Say "Affected End User" "Is (Dynamic)" "Location X Members" where Location X Members is a Script Include that looks for part of a string in a field on a User related list.

It appears there is no easy solution right now, so we are looking into building a DB View and then direct the module to it.

With regards

Anton Vettefyr