Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredJoin 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.
Some background able to table:
The availability comes from a feed which only have rows for (8557-128) = 8429 SKUs.
Which is merged on the product table with 25000+ SKUs inside Power Query.
The null values are then replaced with "Ukendt".
This is all inside Power Query, so the final ProductTable just contains flat rows with the values. There is only 1 active table in question here.
On the page filter I've removed certain old SKUs so we are left with a total of 8557 SKUs.
The measures above is then from a different data set using direct query to the PBI file which has the above data.
Why is the calculation extremely inaccurate when selecting "Ukendt"? I cannot even grasp where it gets the 657 number from. I need it to say 8557 regardless of the selection 🙂
Am I missing some logic with null values? I thought it wouldn't filter backwards on a table that is merged in Power Query. Shouldn't the table contain the flat information?
@AlexaderMilland , All Product availability only remove filter from that column. Other column filter will remain
You can try all(Product )
or all()
and check
That gives me all the 25000+ SKU's as it removes my filters to get down to the 8557. It does however give me the same result regardless of what [Availability] field i pick. So I guess i need to cleanse another filter somewhere that is tied together with the Availability?
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the October 2025 Power BI update to learn about new features.
| User | Count |
|---|---|
| 76 | |
| 38 | |
| 31 | |
| 27 | |
| 26 |