Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

Reply
PANNEER
Frequent Visitor

Error in filters

Hi friends,

I created a report and published it to the Power BI Service, then integrated it into Dynamics 365. After integration, I’m getting an error on the ID field in filters across all pages stating: ‘This field was deleted from the model and cannot be used as a filter. Anybody please provide steps to fix this issue in Power BI/D365?
PANNEER_1-1765518071518.png

 

4 REPLIES 4
Anand24
Super User
Super User

@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 !!!
LinkedIn

PANNEER
Frequent Visitor

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:

  1. Open the report in Power BI Desktop.

  2. 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.

  3. In Model view, confirm the ID column truly exists (or re-add it with the same name if required).

  4. Clear filters by temporarily duplicating the page, then delete the original page (this removes hidden page/report-level filters).

  5. Save and republish to the same workspace.

  6. 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.


Did it work? ✔ Give a Kudo • Mark as Solution – help others too!
rohit1991
Super User
Super User

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.


Did it work? ✔ Give a Kudo • Mark as Solution – help others too!

Helpful resources

Announcements
November Power BI Update Carousel

Power BI Monthly Update - November 2025

Check out the November 2025 Power BI update to learn about new features.

Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Kudoed Authors