Another popular topic on the message boards of late has been navigation between reports on Dashboards. Most commonly this involves guiding the user to another report/dashboard from a particular value displayed in the results of the initial report, for example, at a financial quarter end you may wish to drill down and see sales figures for the best or worst performers in a ranked list. As long as there is a common value that you include in the two reports then this simple method can be applied to any two reports. In our example we use a list of customers and link to there contact details.

The only complicated part of this is that you need to plan your report hierarchy first as the reports need to be created starting with the last (bottom of the drill down pile) first. The reason for this will be clear in a moment, as my example only links two reports I will start with the second. I need to telephone the client so all I need is their contact name and number, as I want to see these individually according to which customer I select from the list I will need the contacts report to be filtered by the value I choose in the first report, in this sample data the common field is the Customer.Name, granted in real life this is more likely be an ID, this field needs to be filtered using an ‘Is Prompted’ filter type.

The sharp eyed amongst you will have noticed that the Customer.Name column is used in the filter but is not in the report, this keeps things tidier, we don’t need the name as we will have selected that to get to this report. To add a filtered column in this way hold down the Shift key and click the column name in the usual way, the Create/Edit Filter dialogue will open automatically. Save the report and create the parent report that will be presented to users first.
For simplicity the report has only two columns, NAME and REGIONNAME from the Customer table, NAME is the column we have used for the filter prompt in our child report so that is the value will use to navigate from. In the column properties for NAME we use the Column Format tab and the Value Interaction property, define the interaction Type as Navigate and then use the Browse button to select the Contacts report we created earlier.

If we now add this report to a dashboard, the child report remains linked and will be displayed on a new page within the same dashboard. Alternatively, you may wish to bring to the users attention other details about the customer at the same time, probably the easiest way to do this is to add the child report to a new dashboard, in this instance I shall call it customer detail, add any number of reports to this dashboard with ‘Is Prompted’ filters and they will all display detail for this customer.

Next time I’ll write up on how we make a dynamic heirarchy that changes depending upon the user who logs in.


  1. Hi Adrian

    Do you know of any way that we can set up a “master” view, and a “detail” view, and then when the user clicks on a value in the master report, it filters the detail report based on the value selected?

    It’s like the example you’ve given here, except instead of the master column “navigating” to the detail report, it instead acts as a dashboard prompt, with any other views on that page that have a compatible column set up with an “as prompted” filter then changing their displayed values. I’ve tried working it out from the documentation and from having a play around, but so far I’ve come up blank.



  2. Adrian – just to clarify – is it possible to define a column in a request as being a “dashboard prompt”, i.e. when clicking on it, it passes the clicked value to all the reports that have that column filtered “as prompted” – in case my question wasn’t clear before.



  3. Mark. I must have missed your reply but here is the answer. Analytics does this stuff for you automatically when you have set-up the Repository Business Model Layer.
    You use hierarchies with drill down keys to define the path of navigating.
    The drill down carries the value as a prompt to the next report

Comments are closed.