Forum Discussion
exportToFile: reportLevelFilters AND a single-select slicer's default value → empty page
**Setup:** Power BI Service, workspace on Fabric capacity (not PPU). Export via `exportToFile` (PPTX) from Power Automate. Server-side only — no JavaScript embedding, so `bookmarksManager.capture()` and `report.reset()` are not available to me. Report-level filters work correctly on pages without slicers on the filtered column. **Problem:** on a page with a slicer that has **Require single selection** enabled, the slicer keeps its saved default value, and my filter is applied on top of it. Since both conditions target the same column and the values differ, the intersection is empty and the page exports blank.
"powerBIReportConfiguration": {
"pages": [ { "pageName": "ReportSectionXXXX" } ],
"reportLevelFilters": [
{ "filter": "MyTable/MyColumn eq 'A'" }
]
}
Slicer default is `'B'`. Result: empty page. The only value that exports correctly is `'B'` —the one the slicer already holds. I understand *why* this happens: a report-level filter narrows the values available to a slicer but never changes the slicer's selection, and preexisting filters combine with the new filter using AND. With single selection enabled, the slicer can never be cleared, so the conflict is unavoidable from the report's default state.
**What I'm asking:** is there anything on the API side that resolves this without editing the report?
- Can `defaultBookmark` or `pages[].bookmark` override the slicer's selection during export, or is single selection a formatting property of the visual that a bookmark cannot affect?
2. Is the precedence between a bookmark and `reportLevelFilters` documented anywhere? The only statement I've found is that export filters are applied *in addition to* the current report state, which reads as AND.
3. Is there any payload option that exports a page as if the slicer weren't there — a server-side equivalent of `report.reset()`?
4. Would moving the field into the "Filters on this report" pane change how the export resolves the conflict?
If the answer is "no API-side option exists", a confirmation I can point to would already help — the remaining path is a report-side change (disabling single selection, or an export-only copy of ,the page without the slicer)
Hello,
Sorry for long answer - we decided use new slicers in Reprots ( list slicer, button slicer) these new slicers allow to have blank value. In another page where we have to have single select we will use deep copy
7 Replies
v-achippaCommunity Support
Hi Ceo_psh,
Thank you for reaching out to Microsoft Fabric Community.
Here looks like the issue is because of the existing single select slicer value being applied together with the reportLevelFilters value. Like for example, if the slicer is set to B and the export filter specifies A, both filters are applied, resulting in no matching data and therefore a blank page.
- Create an export only report page without that slicer and apply reportLevelFilters to it. Alternatively, save the slicer with the required value before exporting.
Thanks and regards,
Anjan Kumar ChippaThanks v-achippa — that matches what I was seeing.
One follow-up so I can close this off: can you confirm that `defaultBookmark` /`pages[].bookmark` in the `exportToFile` payload cannot override a single-select slicer either?
My understanding is that single selection is a formatting property of the visual, so a bookmark can capture a different selected value but can never produce a "nothing selected" state for such a slicer — meaning there is no API-side workaround at all, and the export-only page is the only viable option when the filter value is dynamic per export.
(Saving the slicer with the required value before exporting isn't an option in my case — the value differs for every export request, so it would mean writing to a production report on each run.)
- v-achippa
Hi Ceo_psh,
Yes, your understanding is correct. The bookmark can preserve a slicer selection, but it cannot provide a ‘no selection’ state when require single selection is enabled.
Since the slicer value is dynamic for each export, there is no API side option in exportToFile to clear or ignore that existing slicer selection. So the recommended approach is to use a separate export only page without the single select slicer and apply reportLevelFilters to that page.
Thanks and regards,
Anjan Kumar Chippa - LumericVisuals
Helper II
I don't have documentation-level confirmation of the exact precedence, but from how exportToFile behaves in practice, defaultBookmark sets the report's starting state, and reportLevelFilters layer on top of that.
So a bookmark that sets the slicer's selection to the same value as your export filter should remove the conflict, since bookmarks do capture single-select slicer state — they just can't clear it to nothing, same limit as report.reset().
That's lighter than disabling single-selection or duplicating the page, but it's still a one-time report-side edit, not a pure payload-only fix.
Worth testing since it's non-destructive: add the bookmark, point defaultBookmark at it, and see if the intersection resolves the way you'd expect.
