Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
I'm working on a headcount/attrition report with two primary tables: Headcount and Offboardings. Each table is granular to location, headcount type, and month.
Example of Headcount table (vastly oversimplified - consider many more regions, many more months, etc):
| Month | Region | Type | Headcount |
| 9/1/2017 | US | Management | 101 |
| 9/1/2017 | US | Security | 64 |
| 9/1/2017 | Europe | Management | 110 |
| 9/1/2017 | Europe | Security | 50 |
| 10/1/2017 | US | Management | 112 |
| 10/1/2017 | US | Security | 60 |
Example of Offboarding table (vastly oversimplified - consider many more regions, many more months, etc):
| Month | Region | Type | Offboardings |
| 9/1/2017 | US | Management | 7 |
| 9/1/2017 | US | Security | 2 |
| 9/1/2017 | Europe | Management | 3 |
| 9/1/2017 | Europe | Security | 12 |
| 10/1/2017 | US | Management | 2 |
| 10/1/2017 | US | Security | 5 |
I'm attempting to put together a chart where bars show total headcount month-over-month, and in overlayed lines show the percentage attrition per month based on a calculation. In the example above, this would mean in September we had 24 total offboardings and 325 total headcount = 7.38% attrition. I have created a measure in the Headcount table that performs this calculation: SUM(Offboardings)/SUM(Headcount). This works just fine when there are no filters applied.
The issue lies when I create slicers for Region and for Type. When I select the slicer for Region, it only applies the filter to the headcount table and not to the offboarding table. This causes my calculation to get really out of whack (it would consider ALL offboardings regardless of region, divided by only headcount for the selected region, etc.)
How can I get the measure to consider the filter for both the numerator and denominator?
Solved! Go to Solution.
Turns out my filter was based on only one table and the tables weren't linked with common regions and types. Fixed by creating a table to link the variables.
Turns out my filter was based on only one table and the tables weren't linked with common regions and types. Fixed by creating a table to link the variables.
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Check out the July 2026 Power BI update to learn about new features.
Join Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.
| User | Count |
|---|---|
| 31 | |
| 30 | |
| 27 | |
| 24 | |
| 16 |
| User | Count |
|---|---|
| 57 | |
| 36 | |
| 27 | |
| 24 | |
| 20 |