Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
Solved! Go to Solution.
@arp2 Updated your PBIX, attached below signature. Your Week to Week relationship is inactive so you need to use USERELATIONSHIP in a measure.
Projected Capacity Measure = CALCULATE(SUM('Table2'[Projected Capacity]), USERELATIONSHIP(Table1[Week], 'Table2'[Week]))
@arp2 Generally this means that there is a missing relationshp in the model.
The dummy PBI file is available at following link.
https://1drv.ms/u/s!Ag_LqrJ6gGmfllbA6ZrdJLdiGkQL?e=WEvQwb
What's happening is, when I add Capacity/Projected Capacity to secondary Y axis, it is summing the value for selected discipline for all weeks in table and showing flat line (summed number) whereas I want weekly number in the chart
@arp2 Right and I'm saying that is generally because there is a missing relationship between 2 tables and thus all of the rows in that second table are in context versus being filtered to the correct rows via the relationship.
@Greg_Deckler Got that! I tried but I am unable to solve it. Can you plz have a look at PBI dummy? https://1drv.ms/u/s!Ag_LqrJ6gGmfllbA6ZrdJLdiGkQL?e=WEvQwb
@arp2 Updated your PBIX, attached below signature. Your Week to Week relationship is inactive so you need to use USERELATIONSHIP in a measure.
Projected Capacity Measure = CALCULATE(SUM('Table2'[Projected Capacity]), USERELATIONSHIP(Table1[Week], 'Table2'[Week]))
User | Count |
---|---|
98 | |
90 | |
82 | |
73 | |
67 |
User | Count |
---|---|
115 | |
102 | |
98 | |
71 | |
67 |