Hide Filter in drill through report
22 April, 2013
Hi,
I want to hide a filter in a drill through (child) report. In thread=126163 the following is mentioned "When you using a user-prompt filter, this always gives the user the option to change the selection... You should not be using a user-prompt filter and can be changed at the filter setup page (see below)" .
But I do not want to have my filter having a pre-defined value (which is the other filter option). Via a drill-through I want the user to be able to set filters. But I do not want the user to see the filter. Because this report is not only available as a drill-through (child) report, but also as a report which can be run without selecting the parent report first.
Is there a workaround available?
Greetings,
Eddy
I want to hide a filter in a drill through (child) report. In thread=126163 the following is mentioned "When you using a user-prompt filter, this always gives the user the option to change the selection... You should not be using a user-prompt filter and can be changed at the filter setup page (see below)" .
But I do not want to have my filter having a pre-defined value (which is the other filter option). Via a drill-through I want the user to be able to set filters. But I do not want the user to see the filter. Because this report is not only available as a drill-through (child) report, but also as a report which can be run without selecting the parent report first.
Is there a workaround available?
Greetings,
Eddy
Hi Eddy,
Unfortunately there is no work around available as this is how related reports were built.
Obviously the child report will need to have a user-entry filter so that the parent report can pass the filter across. However it also means that opening the child report directly will also allow you to choose the filter value.
This is not a common setup, as we would expect if the user is able to drill to the child (using values from the parent) then they should also be able to open that child and select the same values from a drop-down list.
Is there are reason why you do not want the user to choose the filter value?
Also, if the user opens that child report, what filter value should be applied? As the filter will need to be hard-coded so no user entry is available.
Helping us understand what you are exactly trying to achieve and why may allow us to find a better way for you.
Regards,
David
Unfortunately there is no work around available as this is how related reports were built.
Obviously the child report will need to have a user-entry filter so that the parent report can pass the filter across. However it also means that opening the child report directly will also allow you to choose the filter value.
This is not a common setup, as we would expect if the user is able to drill to the child (using values from the parent) then they should also be able to open that child and select the same values from a drop-down list.
Is there are reason why you do not want the user to choose the filter value?
Also, if the user opens that child report, what filter value should be applied? As the filter will need to be hard-coded so no user entry is available.
Helping us understand what you are exactly trying to achieve and why may allow us to find a better way for you.
Regards,
David
Thanks for the reply.
So when a user drills down from a parent report, he does not need to see the value of a specific filter in the 'filter' section. This is because he also uses this child report as a stand alone report, and doesn't want to show this specific filter in a filter section. If he doe The value of this filter is already visible in the column.
Greetings
Eddy
So when a user drills down from a parent report, he does not need to see the value of a specific filter in the 'filter' section. This is because he also uses this child report as a stand alone report, and doesn't want to show this specific filter in a filter section. If he doe The value of this filter is already visible in the column.
Greetings
Eddy
Hi Eddy,
I understand that when he drills through he does not want to see the filter, though if he wants to open the report manually without using a filter you would need to use another report that doesn't have a filter.
Unfortunately there is no way around this, it's just how related reports works.
A user entry filter is needed on the child report, this type of filter also requires user-import, so there is no way to hide this.
Apologies for the inconvenience, but I think you will need to have 2 child reports, one you link to from the parent report, and 1 you can just open separately with no filters applied.
Regards,
David
I understand that when he drills through he does not want to see the filter, though if he wants to open the report manually without using a filter you would need to use another report that doesn't have a filter.
Unfortunately there is no way around this, it's just how related reports works.
A user entry filter is needed on the child report, this type of filter also requires user-import, so there is no way to hide this.
Apologies for the inconvenience, but I think you will need to have 2 child reports, one you link to from the parent report, and 1 you can just open separately with no filters applied.
Regards,
David
Ok, thank you for your feedback.
Regards,
Eddy
Regards,
Eddy