Skip to main content
Back to Blog

Power BI ALLEXCEPT Function Guide

Errin O'Connor
8 min read

ALLEXCEPT is a DAX function that removes all filter context from a table except the columns you specify. It is used for percentage-of-parent calculations, running totals that ignore some slicers, and measures that need to stay partially filtered. This guide covers syntax, examples, and when to use ALLEXCEPT vs ALL or ALLSELECTED.

Key Facts

  • ALLEXCEPT syntax: ALLEXCEPT(<table>, <column1>, [<column2>, …])
  • Removes all filters from a table — except the columns you list.
  • Most common use: percentage-of-parent totals (e.g., % of category total).
  • Use ALLEXCEPT inside CALCULATE or DIVIDE for controlled filter removal.
  • EPC Group: Microsoft consulting since 1997. Founder Errin O'Connor authored the bestselling Microsoft Press Power BI book.

Power BI ALLEXCEPT Function: DAX Guide with Examples

Key facts

  • ALLEXCEPT syntax: ALLEXCEPT(<table>, <column1>, [<column2>, …])
  • Removes all filters from a table — except the columns you list.
  • Most common use: percentage-of-parent totals (e.g., % of category total).
  • Use ALLEXCEPT inside CALCULATE or DIVIDE for controlled filter removal.

ALLEXCEPT syntax

ALLEXCEPT takes a table and one or more columns to keep filtered. All other filters on the table are removed.

Related guides and articles

Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group

Why Organizations Choose EPC Group

EPC Group is a Houston-based Microsoft consulting firm with enterprise implementation since 1997 experience and over 10,000 successful deployments across Power BI, Microsoft Fabric, SharePoint, Azure, Microsoft 365, and Copilot. We serve organizations across all industries including Fortune 500, federal agencies, healthcare, financial services, government, manufacturing, energy, education, retail, technology, and global enterprises.

What sets EPC Group apart is our governance-first approach. Every engagement begins with a security and compliance assessment. Our team of senior architects brings hands-on delivery experience across HIPAA, SOC 2, FedRAMP, and CMMC environments. We own outcomes, not hours.

  • Fixed-fee accelerators with predictable pricing and defined deliverables
  • Senior architect engagement on every project, not rotating juniors
  • Compliance-native delivery for regulated industries
  • End-to-end coverage from strategy through managed services
  • 11,000+ enterprise engagements refined into repeatable, risk-controlled patterns

Call (888) 381-9725 or email contact@epcgroup.net for a free assessment.

Power BI Strategy: 2026 Considerations for Power BI Allexcept

Power BI capacity sizing in 2026 starts with the F-SKU economics: F2 ($263/mo) covers small workloads within a 3 GB Direct Lake model-memory limit (Microsoft Learn, Direct Lake overview, read 2026-10-22), F4 ($526/mo) handles a typical mid-market deployment with semantic-model refresh windows under 10 minutes, and F64 (~$8,410/mo (PAYG)) is the sweet spot for enterprises consuming Power BI alongside Microsoft Fabric data engineering, lakehouse storage, and real-time intelligence. Capacity right-sizing should be revisited every 90 days because Microsoft adjusts F-SKU memory allocations, paginated report performance, and Direct Lake mode availability with each major service update.

Direct Lake mode has changed the economics of enterprise Power BI in 2026: instead of importing data into Vertipaq, semantic models now query OneLake-resident Parquet files at near-Import-mode performance without the refresh-window cost. For a Fortune 500 finance organization migrating from a 30-minute Import-mode refresh, the equivalent Direct Lake model typically queries fact data in under 800 ms while removing the entire refresh-orchestration job from Azure Data Factory.

Decision factors EPC Group evaluates

  • Row-level security via service principal authentication
  • Capacity sizing decision (F2/F4/F64+) tied to peak concurrent users and refresh window
  • Copilot grounding quality assessment of semantic-model metadata
  • Direct Lake mode adoption for Fabric-resident semantic models
  • License optimization audit (Pro vs Premium Per User vs F-SKU)

For a tailored read on this topic in your specific tenant, contact EPC Group at contact@epcgroup.net or +1 (888) 381-9725. See pricing and engagement models.

Frequently Asked Questions

When should I use ALLEXCEPT instead of ALL?

Use ALLEXCEPT when you want to remove most filters from a table but preserve a few specific column filters. It's more concise than writing multiple ALL(Column) statements.

Does ALLEXCEPT remove filters from related tables?

No. ALLEXCEPT only removes filters from the table specified in its first argument. Filters propagating through relationships from other tables are not affected.

Can I use ALLEXCEPT outside of CALCULATE?

Technically yes, since it returns a table. However, its primary use is as a CALCULATE filter modifier. Using it outside CALCULATE is an advanced pattern that should be carefully tested.

Why does my ALLEXCEPT measure return the same value for every row?

This usually happens when the columns specified in ALLEXCEPT are not present in your visual's row or column context, causing the measure to remove the grouping filter.

Is ALLEXCEPT affected by bidirectional cross-filtering?

Yes. ALLEXCEPT removes filters regardless of how they arrived, including via cross-filter propagation. Be careful in models with many-to-many relationships and bidirectional filtering.

AI assistant — not a human