Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Dear all,
I am struggling with an analysis that I think should be possible. I have a table with a "date" column (2024 - 2026) a "volume_X" column and a "volume_Y" column. I want to do some analyses where I switch volume amounts between "volume_X" and "volume_Y". In order to do so, I set up three parameters (ranging from -1000 till 1000 with step 100). Each parameter should exchange a certain volume between "volume_X" and "volume_Y" based on the selected parameter value for the a certain year (i.e. parameter 1 exchanges volumes expected in 2024, ..., paramter 3 exchanges volumes expected in 2026).
For example for 2024 I created first a measures to only show the volumes for X and Y for 2024:
volumes_X_2024 = calculate(SUM(volume_X), Table[date] <= date(2024, 12, 31))
volumes_Y_2024 = calculate(SUM(volume_Y), Table[date] <= date(2024, 12, 31))
The problem I face is that when I select a value like +500 (shocked_volume_shift_2024 = 500) using parameter 1 then the +500 is applied on the whole range (2024-2026) and not only on 2024 volumes. So volume_X is increased with 500 over the whole period while volume_Y is decreased with 500 over the whole period. I tried to resolve this by having a binary series where 1s are shown for dates < 2025 and otherwise zero:
binary_series = IF(SUM(Table[Date]) <= DATE(2024,12,31),1,0)
The binary series is then multiplied with the volume shift to only have +500 where date <= 31-12-2024. The measure is:
Dear all,
In addition to the below description and input data table hopefully the below screenshot provides some clarification:
Problem:
The measure shocked_volume_X_shift is first of all not responsive to any date filters applied in the above figure. Also, in the card visual a value of zero is shown eventhough the figure clearly shows that the measure does have a non-zero value at some dates in 2024 (no filter is applied to the card visual). I would expect that the card visual would have a value of 350.
Hope anyone could help clarify the issue and ideally provide a solution. Please let me know whether anything is unclear.
Best,
Marc
Do you want to apply your parameter slicer to the Volume or to the base shift? Are the slicer values applied to X and the inverse to Y, or the other way round?
Hi Ibendlin,
I want to apply the shocks directly to the volume (the cumulative sum of the shock amount X for example for 2024 is added to the volume X). Indeed the slicer values in your image will be the shock values for X and the the inverses to Y (i.e. we exchange volume X for volume Y).
Do let me know whether you need further clarification.
Best,
Marc
Thank you for your quick response. Indeed this gives the desired result for the line-graph, but I wish to be able to show in a card visual the shock amount that is added in total for example for 2024 volume X. For example inserting the measure "volumex" in the card visual makes the shown number non-responsive when I adjust the slider values.
Do you perhaps know how to fix this? Also is the proposed solution easily scalable if I have for example multiply volume categories (i.e. x, y and z)?
Thank you
I don't see what the expected result would be for the card visual? "volumex" only makes sense for individual dates.
If you have more than two categories then how do you plan to distribute the over/under?
Given the measure
If I want to present for example the base volume X delta for 2024 then I can simply create a card visual with the "Base_shift_Volume_X" as input and a filter to only show dates with year 2024.
You need some sort of aggregation to put that value in a card visual.
Hi all,
The below table is used to illustrate the problem I am having. This table is imported as Input_Table, where I add a year_date column ( YEAR(Input_Table[Date]) ). Then I set up a numeric range parameter, for example for 2024:
| Date | Volume_X | Volume_Y | Base_shift_Volume_X | Base_shift_Volume_Y |
| 30/06/2024 | 5000 | 11000 | 100 | 720 |
| 31/07/2024 | 5100 | 11720 | 40 | 460 |
| 31/08/2024 | 5140 | 12180 | 20 | 720 |
| 30/09/2024 | 5160 | 12900 | 100 | 600 |
| 31/10/2024 | 5260 | 13500 | 80 | 360 |
| 30/11/2024 | 5340 | 13860 | 20 | 160 |
| 31/12/2024 | 5360 | 14020 | 40 | 720 |
| 31/01/2025 | 5400 | 14740 | 80 | 320 |
| 28/02/2025 | 5480 | 15060 | 40 | 60 |
| 31/03/2025 | 5520 | 15120 | 100 | 840 |
| 30/04/2025 | 5620 | 15960 | 100 | 640 |
| 31/05/2025 | 5720 | 16600 | 80 | 620 |
| 30/06/2025 | 5800 | 17220 | 40 | 780 |
| 31/07/2025 | 5840 | 18000 | 40 | 800 |
| 31/08/2025 | 5880 | 18800 | 60 | 40 |
| 30/09/2025 | 5940 | 18840 | 20 | 980 |
| 31/10/2025 | 5960 | 19820 | 100 | 500 |
| 30/11/2025 | 6060 | 20320 | 60 | 20 |
| 31/12/2025 | 6120 | 20340 | 80 | 840 |
| 31/01/2026 | 6200 | 21180 | 80 | 20 |
| 28/02/2026 | 6280 | 21200 | 100 | 700 |
| 31/03/2026 | 6380 | 21900 | 0 | 0 |
| 30/04/2026 | 6380 | 21900 | 100 | 340 |
| 31/05/2026 | 6480 | 22240 | 80 | 480 |
| 30/06/2026 | 6560 | 22720 | 100 | 220 |
| 31/07/2026 | 6660 | 22940 | 20 | 780 |
| 31/08/2026 | 6680 | 23720 | 100 | 700 |
| 30/09/2026 | 6780 | 24420 | 20 | 840 |
| 31/10/2026 | 6800 | 25260 | 0 | 220 |
| 30/11/2026 | 6800 | 25480 | 40 | 700 |
| 31/12/2026 | 6840 | 26180 | 20 | 20 |
Hi Ibendlin, please find below the input data (Input_Table). As an example to demonstrate the issue I face, I created the following measures/colums/tables (for 2024 only):
If I select for example exchange_volume_parameter_2024 Value = 10 (via the slicer) then a line chart of shocked_shift_volume_X_2024 shows a shock amount only for 2024 but when I create a card visual with shocked_shift_volume_X_2024 then the shown value is zero. If in this card I add the Date column of Results as filter and only select one date (i.e. 31-7-2024) then I get a value 10, but if I would select all dates in 2024 I get a value of zero while I would expect a value 70 (number of remaining months in 2024 * 10).
| Date | Volume_X | Volume_Y | Base_shift_Volume_X | Base_shift_Volume_Y |
| 30/06/2024 | 5000 | 11000 | 100 | 720 |
| 31/07/2024 | 5100 | 11720 | 40 | 460 |
| 31/08/2024 | 5140 | 12180 | 20 | 720 |
| 30/09/2024 | 5160 | 12900 | 100 | 600 |
| 31/10/2024 | 5260 | 13500 | 80 | 360 |
| 30/11/2024 | 5340 | 13860 | 20 | 160 |
| 31/12/2024 | 5360 | 14020 | 40 | 720 |
| 31/01/2025 | 5400 | 14740 | 80 | 320 |
| 28/02/2025 | 5480 | 15060 | 40 | 60 |
| 31/03/2025 | 5520 | 15120 | 100 | 840 |
| 30/04/2025 | 5620 | 15960 | 100 | 640 |
| 31/05/2025 | 5720 | 16600 | 80 | 620 |
| 30/06/2025 | 5800 | 17220 | 40 | 780 |
| 31/07/2025 | 5840 | 18000 | 40 | 800 |
| 31/08/2025 | 5880 | 18800 | 60 | 40 |
| 30/09/2025 | 5940 | 18840 | 20 | 980 |
| 31/10/2025 | 5960 | 19820 | 100 | 500 |
| 30/11/2025 | 6060 | 20320 | 60 | 20 |
| 31/12/2025 | 6120 | 20340 | 80 | 840 |
| 31/01/2026 | 6200 | 21180 | 80 | 20 |
| 28/02/2026 | 6280 | 21200 | 100 | 700 |
| 31/03/2026 | 6380 | 21900 | 0 | 0 |
| 30/04/2026 | 6380 | 21900 | 100 | 340 |
| 31/05/2026 | 6480 | 22240 | 80 | 480 |
| 30/06/2026 | 6560 | 22720 | 100 | 220 |
| 31/07/2026 | 6660 | 22940 | 20 | 780 |
| 31/08/2026 | 6680 | 23720 | 100 | 700 |
| 30/09/2026 | 6780 | 24420 | 20 | 840 |
| 31/10/2026 | 6800 | 25260 | 0 | 220 |
| 30/11/2026 | 6800 | 25480 | 40 | 700 |
| 31/12/2026 | 6840 | 26180 | 20 | 20 |
Please provide sample data that covers your issue or question completely, in a usable format (not as a screenshot).
Do not include sensitive information or anything not related to the issue or question.
If you are unsure how to upload data please refer to https://community.fabric.microsoft.com/t5/Community-Blog/How-to-provide-sample-data-in-the-Power-BI-...
Please show the expected outcome based on the sample data you provided.
Want faster answers? https://community.fabric.microsoft.com/t5/Desktop/How-to-Get-Your-Question-Answered-Quickly/m-p/1447...
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
Check out the October 2025 Power BI update to learn about new features.