topic Re: Applying filter to ExportToFileInGroup does not work for reports using Import model in Developer

Applying filter to ExportToFileInGroup does not work for reports using Import model

ITM6107 — Thu, 14 Dec 2023 12:42:02 GMT

Hello,

We are attempting to apply a filter to reports using the ExportToFileInGroup API method. See below for code snippet. The filter is applied correctly if the report was created using DirectQuery, but is not applied when using the Import model.

Has anyone been able to successfully apply filters to reports that use Import?

Thanks in advance for any assistance.

Dim groupIdGuid As Guid = New Guid(groupId) Dim reportIdGuid As Guid = New Guid(reportId) Dim exportReportRequest As ExportReportRequest = New ExportReportRequest(fileFormat) If filterList IsNot Nothing AndAlso filterList.Count > 0 Then exportReportRequest.PowerBIReportConfiguration = New PowerBIReportExportConfiguration exportReportRequest.PowerBIReportConfiguration.ReportLevelFilters = New List(Of ExportFilter) For Each filter As String In filterList exportReportRequest.PowerBIReportConfiguration.ReportLevelFilters.Add(New ExportFilter(filter)) Exit For Next End If Dim export As Export = authenticationInfo.powerBIClient.Reports.ExportToFileInGroup(groupIdGuid, reportIdGuid, exportReportRequest)

ExportReportRequest object being passed to the API ExportToFileInGroup (note the ReportLevelFilters[0].Filter property value:

Re: Applying filter to ExportToFileInGroup does not work for reports using Import model

lbendlin — Mon, 18 Dec 2023 00:27:06 GMT

Export To File In Group works off a Semantic Model. At that point it does not matter any more what your data sources were or how you connect to them. Your issue is likely caused by special characters in table or column names, you need to escape them correctly.

Re: Applying filter to ExportToFileInGroup does not work for reports using Import model

DS1415 — Mon, 18 Dec 2023 12:10:48 GMT

Thank you for the response, but this is not the case.

As mentioned above, the same exact filter behaves differently depending on how the data are linked to the report. If the report is configured using Import mode, the filter is not applied and all data are returned. If the report is configured using DirectQuery, the filter is applied correctly.

There is no change in the filter when applying to the two reports.

Re: Applying filter to ExportToFileInGroup does not work for reports using Import model

lbendlin — Mon, 18 Dec 2023 12:41:14 GMT

Do you have non-functional RLS on the import mode source?

Re: Applying filter to ExportToFileInGroup does not work for reports using Import model

DS1415 — Mon, 18 Dec 2023 13:00:02 GMT

No.

The two reports are configured and designed exactly the same way, pointing to the same data source. The only difference is in the data load mode - Import vs DirectQuery.

Re: Applying filter to ExportToFileInGroup does not work for reports using Import model

lbendlin — Mon, 18 Dec 2023 17:00:12 GMT

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .

Re: Applying filter to ExportToFileInGroup does not work for reports using Import model

DS1415 — Mon, 18 Dec 2023 17:15:45 GMT

Thank you.

We will try these options.

Re: Applying filter to ExportToFileInGroup does not work for reports using Import model

AmosHersch — Tue, 19 Dec 2023 06:32:49 GMT

@DS1415 one last suggestion is trying to open the same report in Power BI portal and use the same filter string in the broswer URL as described here Filter a report using query string parameters in the URL - Power BI | Microsoft Learn

The API should apply the filter the same way as Power BI web portal does when appending to the URL.

I am not aware of any limitation for import mode in these regards.

Re: Applying filter to ExportToFileInGroup does not work for reports using Import model

ITM6107 — Tue, 19 Dec 2023 14:38:00 GMT

Thank you for the response. It appears the issue is related to table names containing embedded spaces and not the data load mode.. The link you provided helped us isolate the problem.