topic Re: Issue with Applying Page Filters in Power BI ExportTo API in Developer

Issue with Applying Page Filters in Power BI ExportTo API

jay-sr — Mon, 02 Dec 2024 09:37:01 GMT

Hello Community,

I am facing an issue while trying to export a Power BI paginated report using the ExportTo API with date filters applied. Despite passing the filters in the reportLevelFilters as part of the request body and also tried using the URL based filter, the API does not seem to respect the filters, and the exported report includes all data, ignoring the date constraints.

Here is the API endpoint and request payload I am using:

API Endpoint:

POST https://api.powerbi.com/v1.0/myorg/groups/{workspaceId}/reports/{reportId}/ExportTo

Request Body:

{
    format: 'PDF',
    powerBIReportConfiguration: {
        reportLevelFilters: [{
            filter: `order_details/Billing Cycle in ('Cycle 1', 'Cycle 2')`
        }],
        pages: [
            {
                pageName: pageName
            }
        ]
    }
};

Here is the catch, the filter (order_details/) here is in the page not on the report level filter.

Objective:

I want to filter the data in the exported paginated report to include only rows where the billing cycle in Cycle 1, Cycle 2 (order_details table). However, the report exports with all the data, completely ignoring the filter.

What I Have Tried:

I have get the iframe using the credentials and put this filter over there and it is running fine.
Verified that the Power BI workspace, report ID, and access token are correct.

Issue:

No matter what I try, the exported report does not respect the filters for filtering. It always exports the full dataset instead of applying the billing cycle filter.

Questions:

Is there a specific format for passing page level filters for paginated reports?
Does the ExportTo API support page level filters for paginated reports? If yes, how should the request body be structured?
Has anyone successfully applied date filters in a similar scenario? If so, could you share the correct approach?

Any guidance or suggestions to resolve this issue would be greatly appreciated. Thank you in advance for your help!

Best regards,
Jay Kanara

Re: Issue with Applying Page Filters in Power BI ExportTo API

lbendlin — Mon, 02 Dec 2024 22:09:58 GMT

Your filter is ignored because you did not escape the special characters in the table name and column name.

Filter a report using query string parameters in the URL - Power BI | Microsoft Learn

Re: Issue with Applying Page Filters in Power BI ExportTo API

jay-sr — Tue, 03 Dec 2024 05:33:57 GMT

Hello @lbendlin Thank you for taking the time to respond and provide guidance. I truly appreciate your effort to help.
I’ve tried several approaches with the filters, such as:

reportLevelFilters: [{
    filter: `order_details/Attempt00x20Count in ('1', '2')`
}]

reportLevelFilters: [{
    filter: `order_details/Attempt_00x20_Count in (1, 2)`
}]

reportLevelFilters: [{
    filter: `order_details/Attempt00x20Count in (1, 2)`
}],

reportLevelFilters: [{
    filter: `order_details/Attempt_00x20_Count in ('1', '2')`
}],

Unfortunately, none of these approaches worked for me. I wanted to clarify that this filter is meant to be applied at the page level, not the report level.

If you have any further insights or suggestions on how to structure the filter correctly for page-level filtering, I would be extremely grateful. Thank you again for your time and assistance!

Best Regards,
Jay Kanara

Re: Issue with Applying Page Filters in Power BI ExportTo API

lbendlin — Tue, 03 Dec 2024 13:32:27 GMT

Please read the documentation again. Your encoding style is incorrect.

There is no such thing as page level filters for this scenario. Filters are applied to the data model as a whole.

Re: Issue with Applying Page Filters in Power BI ExportTo API

jay-sr — Tue, 03 Dec 2024 18:33:54 GMT

Hello @lbendlin ,

I have finally resolved the issue! It turns out the problem was not related to the encoding or syntax of the filter. Instead, it was due to a mismatch between the data accepted by Power BI and the data available in the data models.

Thank you once again, @lbendlin , for your response and guidance—it helped me stay on track to identify the root cause.

Best regards,
Jay Kanara