This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
After I published a page in power bi, all the filters in that table disappear. Even with i change the filter to filter to visual to filter to this page, those filters on that particular table still did not get applied. Anyone know why?
Solved! Go to Solution.
Hi @epang
This issue usually happens because Persistent Filters or the "Keep all filters" toggle is overriding your layout during the publishing process. When you publish a report, Power BI Desktop saves the exact state of the filters at the moment of publishing as the new default baseline; however, if your report consumers (or you) have previously viewed the report in the service, the browser often caches your old session filters and ignores the new ones you just uploaded. To fix this, open the report in the Power BI Service and click the "Reset to default" button at the top of the menu bar to force the page to fetch your newly published configuration.
Additionally, check the behavior of your cross-filtering settings inside Power BI Desktop before your next publish. If you look at the Filter Pane settings for that specific table visual, make sure that the "Allow users to change filter type" option is enabled and that the filters aren't accidentally locked or hidden. If you are using a specific table visual that is meant to receive filters from other pages, ensure you haven't toggled off the "Keep all filters" option in the Drill-Through or Page-Level settings section, as turning that off completely blocks incoming filters from being passed to the target table when a user navigates to the page.
Hi @epang,
Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to @RossEdwards & @Poojara_D12 & @Kedar_Pande for sharing valuable insights.
Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.
Thank you for being part of the Microsoft Fabric Community.
Try this: lock your filters in the filter pane before publishing. In Desktop, go to the filter pane, apply your filters, then set them to "lock" so users can't change them. Then republish.
Hi @epang
This issue usually happens because Persistent Filters or the "Keep all filters" toggle is overriding your layout during the publishing process. When you publish a report, Power BI Desktop saves the exact state of the filters at the moment of publishing as the new default baseline; however, if your report consumers (or you) have previously viewed the report in the service, the browser often caches your old session filters and ignores the new ones you just uploaded. To fix this, open the report in the Power BI Service and click the "Reset to default" button at the top of the menu bar to force the page to fetch your newly published configuration.
Additionally, check the behavior of your cross-filtering settings inside Power BI Desktop before your next publish. If you look at the Filter Pane settings for that specific table visual, make sure that the "Allow users to change filter type" option is enabled and that the filters aren't accidentally locked or hidden. If you are using a specific table visual that is meant to receive filters from other pages, ensure you haven't toggled off the "Keep all filters" option in the Drill-Through or Page-Level settings section, as turning that off completely blocks incoming filters from being passed to the target table when a user navigates to the page.
When your model is in the Service, its use of credentials may differ from your local power bi desktop. I would guess that the user name that is used in the service does not have access to the same records as your local Power BI desktop (in data source settings).
If your model is direct query, this will matter immediately. If your model is import, it will carry up the data from your publish and then the issue will present itself after you refresh.
If you are using a deployment pipeline, only the metadata is transferred. In that specific case, your issue may simply be that your model requires a refresh.
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 29 | |
| 28 | |
| 25 | |
| 20 | |
| 14 |
| User | Count |
|---|---|
| 53 | |
| 47 | |
| 29 | |
| 20 | |
| 19 |