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!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Hello, been working on this type of model.
employee table contains primarily: employee info dept, line of business etc.
Problem table: has all the records reported as a problem which is all unique values
Incident table: May contains multiple Incident IDs for a certain Problem ID
my intent is to filter the problem table and employee table vise versa . Like, know how many PROBLEM IDs came from a certain location, dept, line of business ..
currently, there are no common fields between the two. However, there is a requesterID coming from the Incident table which I can probably use to merge into a reference Problem table and eventually another merge to employe table which end with duplicate values
I was hoping to achieve that WITHOUT using the bi-directional filtering
Solved! Go to Solution.
Hi @v_mark you can use the TREATAS() function to simulate a relationship when no relationship exists.
Your syntax would be something along the lines of
CALCULATE(
[Measure],
TREATAS(Incident[RequesterID], Problem[Employee???})
)
Hope this helps! 🙂
Hi @v_mark you can use the TREATAS() function to simulate a relationship when no relationship exists.
Your syntax would be something along the lines of
CALCULATE(
[Measure],
TREATAS(Incident[RequesterID], Problem[Employee???})
)
Hope this helps! 🙂
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 52 | |
| 50 | |
| 34 | |
| 15 | |
| 14 |
| User | Count |
|---|---|
| 93 | |
| 77 | |
| 41 | |
| 26 | |
| 26 |