Join 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!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
I have a visual with takes minutes to load… I am using 3 columns;
First column I am using this solution:
https://www.sqlbi.com/articles/handling-customers-with-the-same-name-in-power-bi/
Which is:
Name Unique =
VAR CustomersWithSameName =
CALCULATETABLE (
SUMMARIZE ( Customer, Customer[Customer Code], Customer[Name] ),
ALLEXCEPT ( Customer, Customer[Name] )
)
VAR Ranking =
RANKX ( CustomersWithSameName, Customer[Customer Code],, ASC, DENSE )
VAR Blanks =
REPT ( UNICHAR ( 8204 ), Ranking - 1 )
VAR Result = Customer[Name] & Blanks
RETURN
Result
The other 2 columns are
CALCULATE(
DISTINCTCOUNT(Fact[K_Parent_Customer])
,FILTER(Fact,Fact[Revenue] <> 0
)
)
And
CALCULATE(
DISTINCTCOUNT(Fact[K_Customer])
,FILTER(Fact,Fact[Revenue] <> 0
)
)
Why is it takig so long? is there perhaps another option to avoid the duplicates in the 1st column?
Hi @Anonymous it could be part below as you filter Fact, which is not best practice. In addition, part <>0 in Fact table: usually if there is no Revenue in Fact then there is no related Customer, so it seems <>0 should be removed.
Try without Fitler part and see performance.
,FILTER(Fact,Fact[Revenue] <> 0
Proud to be a Super User!
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the September 2025 Power BI update to learn about new features.
User | Count |
---|---|
9 | |
8 | |
7 | |
4 | |
3 |