Skip to Content
0
Former Member
Jun 16, 2016 at 01:51 PM

What is the difference between report-filter and block-filter?

936 Views

Hello,

the more I try and test, the more question occur. Today, I found a difference between using the same filter (by controls) on report and on block level.

Again, I have a two DP from an Excel file, merged on customer-id and employee-id. Here you can see the structure and content of the DP, no filters applied:

The measure variable is not relevant (I guess), it was a detail before, causing very strange and unexpected results. May be part of later discussion.

The left and middle table were auto-generated from the DP. I have activated the options to show empty dimensions and not aggregate and deactivated the extended merge option in the settings.

Now, my expectation is that the displayed content of table/block 1 (DP1) is not at all affected by any filter I define for object [Tab] of DP2.

And secondly: if something changes (because of the merge), the same change should happen if the filter is applied to the report or to all blocks of the report.

I have created 2 controls to filter for [Tab]="A". The first (Tab - Report 1) is applied to the report level, while the second (Tab - all blocks) affects only all three blocks at the lower level. When applied on report level, I get all data from the table - compared to a left join on [Emp Id], which is dimension used in the merge:

But when applied on block level, I only get a value for each [Emp Id] that is also contained in DP2 where [Tab] = "A":

Can anyone please explain why this happens? What did I miss?

In a nutshell:

a) Why does selecting all blocks differ from selecting the report as target (and thus auto-selecting all contained blocks). Is there more to it than just affecting all contained blocks?

b) Why does the merge affect the first block that only shows data from DP1? When I unmerge, all rows are displayed, again.

BR

Michael

Attachments