Supplies are limited. Contact info@espc.tech right away to save your spot before the conference sells out.
Get your discountScore big with last-minute savings on the final tickets to FabCon Vienna. Secure your discount
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! 🙂
User | Count |
---|---|
64 | |
59 | |
47 | |
32 | |
31 |
User | Count |
---|---|
84 | |
73 | |
52 | |
50 | |
44 |