I am looking for an example of a drill down graph portlet. What I am trying to accomplish is -

Portlet one is a Pie graph that has hours in percentage broken down by region. Drill down to portlet Two by clicking on a region in Porlet one's Pie graph.

Portlet two is a Bar graph showing one region and broken down by task and hours. I want to be able to click on one of those tasks and the third portlet would be

Portlet Three – A grid portlet showing the resources and hours for that one task or all the tasks for that region.

The attachment I have included is what I am looking to do but it was down by extracting data from Clarity into Excel and creating the graphs in Excel.

So is what I am looking to do possible? Can anyone point me to an example? Or is this only possible with Grid portlets?

I hope this makes sense. If you look at the attachment I have included I think it is more obvious.

Peter Maino

Portlet one is a Pie graph that has hours in percentage broken down by region. Drill down to portlet Two by clicking on a region in Porlet one's Pie graph.

Portlet two is a Bar graph showing one region and broken down by task and hours. I want to be able to click on one of those tasks and the third portlet would be

Portlet Three – A grid portlet showing the resources and hours for that one task or all the tasks for that region.

The attachment I have included is what I am looking to do but it was down by extracting data from Clarity into Excel and creating the graphs in Excel.

So is what I am looking to do possible? Can anyone point me to an example? Or is this only possible with Grid portlets?

I hope this makes sense. If you look at the attachment I have included I think it is more obvious.

Peter Maino

"Portlet 1" sits on a Clarity page (any)

Clicking on a segment in "Portlet 1" links to a Clarity portlet page (lets call it "Page 2") which takes as a parameter the segment that was clicked on.

On "Page 2" is "Portlet 2", which uses the page parameter as part of its NSQL query

Clicking on a column in "Portlet 2" links to another Clarity portlet page (lets call it "Page 3") which takes as a parameter the column that was clicked on.

On "Page 3" is "Portlet 3", which uses the page parameter as part of its NSQL query

--

The "trick" is that it is portlet pages that take the parameters (you can actually see the parameter values on the page URL), but the portlet's NSQL query is what actually uses the parameter value.

Once you have got it to work once, it all makes sense and become quite easy to do! :grin: