Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
Table Name: TableBI
Wave | Company Index | Company ID | Weights | Questions | Answers | Weighted Answers | Periods |
1 | 1 | 1-1 | 0,006 | Demand change compared to the previous 6 months | -1 | -0,006 | 2022 H2 |
1 | 1 | 1-1 | 0,006 | Expected change in demand in the next 6 months | 1 | 0,006 | 2023 H1 |
1 | 1 | 1-1 | 0,006 | Liquidity problems intensity | 1 | 0,006 | 2022 H2 |
1 | 1 | 1-1 | 0,006 | Expected change in employment | 0 | 0 | 2023 H1 |
1 | 2 | 1-2 | 0,001 | Demand change compared to the previous 6 months | 1 | 0,001 | 2022 H2 |
1 | 2 | 1-2 | 0,001 | Expected change in demand in the next 6 months | 1 | 0,001 | 2023 H1 |
1 | 2 | 1-2 | 0,001 | Liquidity problems intensity | -1 | -0,001 | 2022 H2 |
1 | 2 | 1-2 | 0,001 | Expected change in employment | 1 | 0,001 | 2023 H1 |
1 | 3 | 1-3 | 0,0057 | Demand change compared to the previous 6 months | 1 | 0,0057 | 2022 H2 |
1 | 3 | 1-3 | 0,0057 | Expected change in demand in the next 6 months | 0 | 0 | 2023 H1 |
1 | 3 | 1-3 | 0,0057 | Liquidity problems intensity | 0 | 0 | 2022 H2 |
1 | 3 | 1-3 | 0,0057 | Expected change in employment | 0 | 0 | 2023 H1 |
2 | 1 | 2-1 | 0,006 | Demand change compared to the previous 6 months | 1 | 0,006 | 2023 H1 |
2 | 1 | 2-1 | 0,006 | Expected change in demand in the next 6 months | 0 | 0 | 2023 H2 |
2 | 1 | 2-1 | 0,006 | Liquidity problems intensity | 0 | 0 | 2023 H1 |
2 | 1 | 2-1 | 0,006 | Expected change in employment | 0 | 0 | 2023 H2 |
2 | 2 | 2-2 | 0,001 | Demand change compared to the previous 6 months | 1 | 0,001 | 2023 H1 |
2 | 2 | 2-2 | 0,001 | Expected change in demand in the next 6 months | 1 | 0,001 | 2023 H2 |
2 | 2 | 2-2 | 0,001 | Liquidity problems intensity | -1 | -0,001 | 2023 H1 |
2 | 2 | 2-2 | 0,001 | Expected change in employment | 1 | 0,001 | 2023 H2 |
2 | 3 | 2-3 | 0,0057 | Demand change compared to the previous 6 months | 1 | 0,0057 | 2023 H1 |
2 | 3 | 2-3 | 0,0057 | Expected change in demand in the next 6 months | 0 | 0 | 2023 H2 |
2 | 3 | 2-3 | 0,0057 | Liquidity problems intensity | -1 | -0,0057 | 2023 H1 |
2 | 3 | 2-3 | 0,0057 | Expected change in employment | 1 | 0,0057 | 2023 H2 |
*Weighted Answers is calculated as: Weights * Answers
**In the column "Answers" -1 denotes decrease (or zero problems for Liquidity problems intensity), 0 denotes stability (or low to medium intensity problems), and 1 denotes increase (or high intensity problems).
(1) SelectedQuestion1 = "Liquidity problems intensity"
SelectedQuestion2 = "Expected change in demand in the next 6 months"
SelectedPrice = 1
The result should be: [0,006 + (-0,001) + (-0,001)] / (0,006 + 0,001 + 0,001) = 0,5
(This is working!)
(2) SelectedQuestion1 = "Liquidity problems intensity"
SelectedQuestion2 = "Expected change in demand in the next 6 months"
SelectedPrice = 0
The result should be: [0 + 0 + (-0,0057)] / (0,0057 +0,006 + 0,0057) = -0,32759
(This is NOT working!)
Hi @atziovara must ask: why your weighter avg. is not simple weighted avg., meaning why
not use something like SUMX( 'TableBI','TableBI'[Weights]*'TableBI'[Answers]) or similar?
Proud to be a Super User!
@some_bih Thank you for your response!
The formula for the Weighted Averagethat I am using is a simple one!
It just sums the weighted answers (weights * answers) and divides the total by the sum of the weights. I am using the typical mathematical formula:
Weighted Mean = Σ (wi * xi) / Σwi
The filters that I am trying to use, which are neccesarry for drawing conclusions for business purposes, are creating the issue. I need to compute not only the Weighted Average for all the Questions posed to the companies, but I also for special cases, like "what is the weighted average of Liquidity problems intensity, for companies who expect that their demand will increase/stay stable in the next semester"?
My measure is working perfectly for all cases except when SelectedPrice = 0.
User | Count |
---|---|
16 | |
14 | |
13 | |
12 | |
11 |
User | Count |
---|---|
19 | |
16 | |
15 | |
11 | |
9 |