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.
Is there any differnce in using RELATED or not for the below case? I still cannot follow when its necesary to use it, for example:
VAR = SELECTCOLUMNS( FILTER(Cust,Cust[City] = "LA")
,"CustNo"
,Cust[CustNo] )
Works the same as...
VAR =
SELECTCOLUMNS(
FILTER(
Cust
,RELATED(Cust[City]) = "LA"
)
,"CustNo"
,Cust[CustNo]
)
@Anonymous
RELATED is needed only if the following conditions hold simultaneously:
1. You've got a row context on a certain base table.
2. You want to get a value from a table that is in relation to the one you are iterating over right now (hence the row context) and the table sits on the one-side of the relationship.
This is really all there is to it. Please read the documentation of the function as well https://dax.guide/related
@Anonymous , if you are using cust table, then there is no need to use related. You should use that to bring column from a table from one side of one to many join
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 |
User | Count |
---|---|
15 | |
14 | |
12 | |
10 | |
9 |