Both are based on the same subject area?
The target has 'Is Prompted' filters on all of the columns you are trying to 'catch'?
There is nothing else filter wise on the same columns that could be blocking?
When you say 'navigation' do you mean an action link?
This was just answered yesterday:
The gist of it is, when using an action link to pass multiple filters, use the "Navigate to a web page" option, not the "Navigate to BI content" option.
In addition to the good replies already posted above, it's worth nothing that action links do different things based on what/where they are applied. An action link on an attribute column will act in a very different way than an action link on a measure column.
As a general note you maybe want to have a look at How to Ask Questions in Developer Community Spaces and always post more details about your use case as there are tons of unknowns (starting from the version you talk about as things could work differently from a version to another).
Also as always:
1.) BI Publisher "Report" or OBI "Analysis"? Two different objects in two different technologies!
2.) HOW do you "navigate"? Navigate action? Manually constructed URL?
3.) IF it's an analysis - same Subject Area or different?
Yes Action Links.
Ok Let me try.Thanks for your replying.
Yes Same Subject Area.
Yes i constructed URL using the option GO URL Navigation to Web Page. But this navigations needs user to type required values.
let's say i have two dimension columns
1.Request Type --> It has mutiple types values --> KPI Actual & KPI Base
2.Workflow Status --> RUnning , Not Completed, Not Achieved, Partially Achieved.
So now user want to see based on Request Type values any of the Workflow status values
In HOrizontal Bar we have KPI ACTUAL as type with 4 workflow status values in different colors. As we click the each color/value it target report filter should filter with Type and Status.
You really don't need to use GO_URL if this is 'drill' behaviour on same subject area.
All you need is 'Is Prompted' on the target report and an action link for navigate to report on the data (not heading)
If you find that one column is ignoring the drill specific to the data then add a local dashboard prompt and use that to set presentation variable value, and filter based on the presentation variable instead on the target for that column. Once you get it to work you can then hide the dashboard prompt on the source page.
yes i agree with you using Presentation Variable using, but Type and WOrkflow Status are not part of Dashboard prompts of main report/dashboard.
Yes, I am not suggesting they should be, I am suggesting you create a separate dashboard prompt on that page and hide it.
So cosmetically the experience will be the same for the end user, but behind the curtain you will have this extra logic.
Oh Ok Sure. Will try this above logic.
I have used this successfully previously.
I also find the view sql / view parameters useful to use on the landing page whilst you are trying to diagnose exactly what is being passed / not being passed.