Fabric Warehouse Semantic Model with Excel Pivot – Recommended Approach for Excel-Centric Reporting?

Hi RonStrasser,

Thanks for sharing the extra details and the reproducible example.

From the behavior you outlined:

• Excel Version 2508 (Build 19127.20622)
• Connection through Power BI semantic model
• The same exclusion filter returns the correct results in Power BI
• The incorrect results appear only in Excel when exclusion-based filtering is used on dimensions with more than 10,000 distinct members
• Excluding a single member removes a much larger portion of the dataset

This does not seem to match the expected behavior of a semantic model, especially since the same filter logic works correctly in Power BI. Since the issue can be reproduced and is specific to Excel, it looks more likely to be related to how Excel handles exclusion filters on large member sets than to the semantic model itself.

At the moment, I am not aware of any published Microsoft documentation that lists this as a known limitation. Because this could affect data accuracy and business decisions, I would suggest opening a Microsoft Support ticket and including:

• The Excel version and build information
• A sample semantic model, if possible
• Steps to reproduce the issue
• Comparison results showing the correct behavior in Power BI and the incorrect behavior in Excel

Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn

As a temporary workaround, many organizations use inclusion-based filters or handle complex filtering in Power BI when working with high-cardinality dimensions. That said, those approaches would only reduce the impact and would not solve the underlying behavior you are seeing.

Regards,
Sahasra