Paginated Report visual insensitive to multi-table slicers

[docdata]

An account table and IAServiceSplit table exist in my model. 

IAServiceSplit is effectively a duplicate of the account table.  account has a column of type list with multiple comma separated values.  IAServiceSplit splits this column on the comma into new rows.  A bidirectional filtering many:1 relationship exists between these two tables.

(if a "contains" slicer or list-type column existed, this model setup wouldn't be needed)

I'm using a Paginated Report visual that takes in Account ID as a parameter (allow multiple values, no default values, no "Available Values", automatically determine when to refresh) to filter a PR visual of accounts and their attributes.

There are Industry (IAServiceSplit[Industry Associations]) and Ultimate Country (account[Ultimate Country]) slicers.  In a regular table/matrix visual, the list of Account IDs is properly filtered (accounting for both slicers).  This is also confirmed by the list of available Account IDs to filter on for the PR visual.  This interaction also works as expected for the rest of the PBI report.

However, the PR only accounts for a single slicer.  If IAServiceSplit[Account ID] is used for the PR parameter, only accounts affected by the Industry Association slicer show, and if account[Account ID] is used for the PR parameter, only accounts affected by the Ultimate Country slicer show (example below).

The desired result is both slicers to create a smaller subset of Account IDs to be used for the final PR filter.  I tried to create a calculated table

INTERSECTION(
    ALLSELECTED(account[Account ID],
    ALLSELECTED(IAServiceSplit[Account ID]
)

 but the resulting table isn't calculated post-slicers.

[v-xianjtan-msft]

Hi @docdata 

According to your description, I think it's because the Paginated report visual can't take into account multiple filters from different slicers at the same time when processing a single parameter.

Please consider adding two parameters to your Paginated report and mapping them to the IAServiceSplit[Industry Associations] and account[Ultimate Country] fields respectively when creating the Paginated report visual in Power BI Desktop.
This way the slicers for both fields will be applied to your Paginated report visual.

No slicers applied:

Apply the first slicer:

Paginated report visual applies the filtering of both slicers at the same time:

Please refer to this link about Paginated report visual: Create and use the paginated report visual - Power BI | Microsoft Learn

Best Regards,
Jarvis Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[docdata]

The PR itself doesn't take in any of the slicers.  The slicers reduce the Account IDs in IAServiceSplit and account, but the PR visual only accounts for the filters applied to the source table for Account IDs.

[v-xianjtan-msft]

Hi @docdata 

Sorry for the late reply.

My test results are consistent with yours. If the PR visual only takes the Account ID as a parameter, the PR visual will not be able to satisfy both slicing choices like the Table/Matrix visual, even if the Account ID Calcultion Table created satisfies both slicing conditions.

FilteredAccounts = 
INTERSECT(
    SELECTCOLUMNS(
        FILTER(
            ALLSELECTED(account),
            [Ultimate Country] IN VALUES(account[Ultimate Country])
        ),
        "Account ID", account[Account ID]
    ),
    SELECTCOLUMNS(
        FILTER(
            ALLSELECTED(IAServiceSplit),
            [Industry Associations] IN VALUES(IAServiceSplit[Industry Associations])
        ),
        "Account ID", IAServiceSplit[Account ID]
    )
)

If you're a Pro account, you can create a support ticket for free and a dedicated Microsoft engineer will solve the problem for you.

How to create a support ticket in Power BI - Microsoft Fabric Community

Thank you for your understanding.

Best Regards,
Jarvis Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.