I want to use Projectrak LoV field as a Dimension in Pages to filter

wojo3 · September 9, 2024, 9:08pm

I have imported the “Phase” field in as a dimension. It is a LoV (Phase 1, Phase 2, Phase 3, etc.).
I created a report with Project as the Row and added Projectrak Phase as the Page such that I can filter by which Phase I want to see.

If I Filter on “Phase 3” I should get 12 results but instead I get multiple projects with varying Phases (see 1st image).

If I click the “Nonempty” button on the Row, it drops the results to only Phase 3 items but there are only 7 instead of 12 (see 2nd image)

Does this have to do with the fact that the Projectrak Phase field is a List of Values drop down field?

jerome_lgr · September 10, 2024, 8:06am

Hi wojo3, maybe you need to have your dimension Projectrak Phase also in Row.

wojo3 · September 10, 2024, 2:19pm

I actually tried that already, thanks - a couple of different ways.
In the example, if leave the 'Nonempty" button off, and I filter for Phase 4, it shows me all projects.

The Projectrak field in Jira is a Dropdown so I feel like this is contributing to the challenge but not sure.

nauris.malitis · September 11, 2024, 2:07pm

Hi @wojo3

Thanks for sharing the details!

In eazyBI Page filters impact the shown rows based on the measures used in the report. That’s why we have a saying “Measure is Treasure!”.

In this report, you’ve selected two Projectrak properties to be displayed in columns, so the default “Issues created” measure is used to determine which rows to display for your selections.

Without the “Nonempty” option enabled, the rows “stay the same” for different page filters, however only the relevant measures are returned. For example, in your first screenshot, if you enabled the “Issues created” measure, you’d see the values only for Phase 3 projects.

Now, when you enable the “Nonempty” option, the report engine returns only those rows where the measure has a value based on the report context. In this case only 7 of the 12 Phase 3 projects are returned, because they have “Issues created” present.

If you’d additionally enable the “Issues created” or any other measure, the Page filter will start to make sense.

Let me know if this explains the filter behavior!

Best regards,
Nauris

wojo3 · September 13, 2024, 8:00pm

In some of these projects there are no issues yet - just planning information from Projectrak.

I did find out that there is an issue with what I want to do due to the fact that the Projectrak Phase item is text and not number based.

The work around I was given was to create a user defined field with the following:

iif(InStr([Measures].[Projectrak Phase],[Projectrak Phase].CurrentHierarchyMember.Name) > 0,1,0)

I called the field “PhaseMatch” and then add a Filter to the chart based on that field where PhaseMatch = 1.
That now allows me to filter by that “Page” item.