I have noticed that when I drill into the data that the time filter is resetting itself? Is this normal functionality, is there something setup incorrectly, or am I doing something wrong?

To explain it better:

The graph I want to use is a tree map. I would expect a drill to pass the time dimension of previous month to the next level. I set a Time Filter to Previous Month.

So the first graph is my top level Business segment dimension showing our four business segments. The next graph would be by our contract services division. It reverts to YTD instead of keeping the previous month filter. Any idea why the time filter is not flowing with my drill?

Here is one answer that I have received.

Some charts can’t handle multiple points in time… pie charts and donuts and tree maps generally only show a single point in time YTD current and prior, current (period/year/quarter/month), prior (period/year/quarter/month), and previous (period/year/quarter/month) are examples of single points in time.


Period means it uses the current time level as passed. That can be set up in gadget preferences for many gadgets, and for those that don’t explicitly use that preference, PMF has a default time level which you can set under Manage > Settings > Summarization.


The code in these is smart enough to use a single point in time that should be compatible with for your request.


There are time series charts that are designed to break out ranges of time as well.

This message has been edited. Last edited by: Jasen,

In the specific situation you're running into, it looks as if the general level filter you're applying is getting overridden by the preferences of the gadget you're drilling on.
There's a subtle problem with the hierarchy that PMF uses when deciding what to apply on a broadcast,

* Defaults control what first displays
* Applying click drills to charts change the context but carry the context from each chart.
* General filters should override these.

And we're not respecting that, so the first time you do the click it's not carried over on the broadcast. It's subtle but confusing and we don't want to be confusing.

Testing this I found a second filter broadcast works as expected - it changes the display state so it goes out over broadcast.

We can do better here... so we'll fix it to make sure that a general filter click is also carried on the very first broadcast you send.

Thanks for your feedback! It makes the product better.

Issue has been fixed. I will close the message.