Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Vote for your favorite vizzies from the Power BI Dataviz World Championship submissions. Vote now!
Hi friends,
Solved! Go to Solution.
Hi @PANNEER ,
Sometimes the broken field still exists in the Report/Page level Filters pane, even if it doesn't appear in any visual or bookmark, so it's worth checking and clearing filters there explicitly. This issue can happen not only when a column is deleted, but also when it's renamed or replaced, while downstream systems like Dynamics 365 continue to reference the old field name. In most cases this isn't a Power BI visual bug, but due to Dynamics 365 caching report metadata, which is why simply fixing and republishing the report may not be enough unless the embedded report is removed and added again. Also, follow order, clean the report in Power BI Desktop first, then republish, and only after that re embed it in Dynamics to ensure the cache refresh works correctly.
Hi Friends,
Still i couldn't remove this ID error from D365. Anybody please help me to fix this issue?
Thank you
Hi @PANNEER ,
Sometimes the broken field still exists in the Report/Page level Filters pane, even if it doesn't appear in any visual or bookmark, so it's worth checking and clearing filters there explicitly. This issue can happen not only when a column is deleted, but also when it's renamed or replaced, while downstream systems like Dynamics 365 continue to reference the old field name. In most cases this isn't a Power BI visual bug, but due to Dynamics 365 caching report metadata, which is why simply fixing and republishing the report may not be enough unless the embedded report is removed and added again. Also, follow order, clean the report in Power BI Desktop first, then republish, and only after that re embed it in Dynamics to ensure the cache refresh works correctly.
Hi @PANNEER ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions
Hi @PANNEER ,
I would take a moment to thank @rohit1991 , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions
@PANNEER,
Remove ID field from filter section and pull the ID you want into the section. Since this is a report-level (filters on all pages) filter, one-time change should do it.
Give a Thumbs Up if this post helped you in any way and Mark This Post as Solution if it solved your query !!! Proud To Be a Super User !!! |
I couldn't see the broken ID field from all pages in filters.
Hii @PANNEER
You won’t always see the broken ID field in the Filters pane because it can be orphaned in the report metadata. Try this:
Open the report in Power BI Desktop.
Go to View >> Selection pane and View >> Bookmarks >> check if any bookmark or hidden visual is still using the old ID field and remove it.
In Model view, confirm the ID column truly exists (or re-add it with the same name if required).
Clear filters by temporarily duplicating the page, then delete the original page (this removes hidden page/report-level filters).
Save and republish to the same workspace.
In Dynamics 365, remove the embedded Power BI report and add it again to refresh cached filter metadata.
This usually fixes cases where the filter exists in cache but not visibly in the report UI.
Hii @PANNEER
This error occurs because Dynamics 365 caches Power BI filter metadata. If a column (like ID) that was previously used as a page-level or report-level filter is later renamed, removed, or replaced in the Power BI model, D365 still tries to reference the old field, even though it no longer exists. To fix this, open the report in Power BI Desktop, remove the broken ID filter from all pages, add the correct field if required, republish the report to the same workspace, and then remove and re-add the embedded report in Dynamics 365 to refresh the cached schema.
Vote for your favorite vizzies from the Power BI World Championship submissions!
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 57 | |
| 52 | |
| 45 | |
| 17 | |
| 16 |
| User | Count |
|---|---|
| 108 | |
| 108 | |
| 39 | |
| 33 | |
| 26 |