Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
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! 🙂
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Ask questions in Eventhouse and KQL, Eventstream, and Reflex.
User | Count |
---|---|
84 | |
84 | |
65 | |
62 | |
55 |
User | Count |
---|---|
172 | |
108 | |
105 | |
71 | |
70 |