Hi Team,

I've got a very simple gadget on my dashboard:

-SET &RPT_FLDIN01='INDVRC_ACTUAL_TARGET_DEFAULT';
-INCLUDE PMF_RPT_TMPLT_MEAS_ACRDIM

When I check the preferences of the gadget, it asks for a dimension along the top. I choose Location and it asks for the level. This is where the problem lies. When I choose Location level 1, the gadget works well. I see the first level of my Location dimension along the top and I can click on any measure value and drill to the Measure Detail report. When I choose Location level 2, I lose the ability to drill to the Measure Detail report. I see the second level of my Location dimension along the top, but when I click to drill to Measure Detail, it says there is no data. When I view the source, I see that the query is taking the Location level 2 value and checking it against the Location Level 1:

-* WHERE_DIM01: WHERE (LOCATION_LEVEL01_VALUE EQ '')

Let me know if there is a way I can correct this behaviour.

Cheers,

Joey

Are you using a factory provided gadget or making your own?

If your own, please provide the entire code.

If factory, please tell us the name.

thanks

Hi Bob,

Thanks for the quick response.

I am using a custom gadget, but I've replicated the behaviour with a built-in gadget, too.

Try this with the 'Metric - Dimensional Crosstab Across Measure Grid' gadget, and you should be able to see the same thing that I am seeing.

Cheers,

Joey

OK. I found the problem. This was noticed by someone else and was fixed in PMF 5.2.2.

The fix is interleaved into core architecture and isn't safe to patch, otherwise we'd send you a quick patch.

Can you upgrade?

Hi Bob,

I've tested this in PMF 5.2.2 and I see it is acting the same as before. I wonder if you can double-check that this is actually fixed, because if so, then there is something wrong with our 5.2.2 install.

Please let me know.

Cheers,

Joey

Hey Joey,

I verified this behavior.

What's happening here is that if you want to drill down to a lower level of a dimension, then you have to supply values for the higher levels of that dimension. If you do not supply a higher level values, then PMF uses blank.

In your situation, you've specified a second level sort, but have not filtered on the top level. So the first report runs OK, but when you try to drill down to the detail, it does not have a top level value, so it uses blanks. Hence the

-* WHERE_DIM01: WHERE (LOCATION_LEVEL01_VALUE EQ '')

In order to make this work (initial sort on lower level), you will need to add a filter to the gadget using the same dimension you are sorting on and select a higher level value. So if you are sorting on level 2 of Location value, you must supply a level 1 value in the initial query (e.g., EAST).

That said, you've raised a good point here. We'll look into adding a feature to make this easier in the future.

EricH

Hi Eric,

I actually have a user role that should provide the first dimension level value. Another way of saying this is that the user is already restricted to a particular Location level 1 value. They only see the applicable level 2 values based on the user role's location filter, but the drill-down does not pick up on the user role value.

Is there some code that you can provide to make the drill-down use the user role value for the Level 1 filter?

Cheers,

Joey