Dynamic Parameters for What if analysis
[Will Thompson] I've just merged a couple of very close scenarios, which all have similar great ideas! Something we're considering for the future, so I'm keen to hear your feedback on this. I like this core scenario of a numeric value that is bound to a slider control, and can then be used as part of some expression.
- In a sales report, I can adjust a '% increase' slider to see what impact a small change in revenue might have had on my sales.
- In a mortgage calculator, I can change the % rate, borrowed amount and term to see projected repayments
- In a quota report I might change a 'Opportunity confidence' control to see the likely bonus I could earn at the end of the year.
Please, keep voting and help us prioritize this!
Original suggestions follow:
So this scenario brings what-if-analysis to the visualization without changing the underlying data source. Let's say I have a table that has numeric values (integers, floating values, etc.). I created a chart (column, line, etc.) visual of that table data. Then instead of using SUM, AVG, COUNT, DISTINCT COUNT, I now can use a math expression applied to the numeric value (say I want to see what my chart looks like if I increase sales by 10%). Then I would see the new column in my table (calculated column with new values). I can now add that new column to the chart and graph that, labeling that as 'if sales increased by 10%' to show how that would compared to the actual numbers I see.
Hi everyone! I’m pleased to say this is available in the August update of Power BI Desktop. You can create a table that is bound to a slicer to select a value, and use that value in your calculations.
At the moment it’s not supported in Live Connect mode over SSAS models – if you have a requirement for that scenario please vote here: https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/20558389-enable-what-if-parameters-with-analysis-services
bharat kadepurkar commented
I am trying to create a what if type analysis report in power BI Desktop ( Free version ) however not able to create it as the new parameter what-if button on modelling tab is disabled. Could you please help know me how it can be enabled?
Jorge Diaz commented
We need this on SQL SSAS connections
Great that this feature has been added! This tool is very useful when doing what if analysis with percentage values however not with large numbers. For example I would like to see how the cost of a project (ranging from $1,000-$1,000,000) will affect NPV.
Currently, the visual tool will not support that large of a range. Also, when removing the slider option, the manual input seems to bug out a lot.
German Henriquez commented
It would great if we can save different versions or scenarios of a what if analysis. Sometimes I think power bi should work in same way that sharepoint`s control versión whit extract from the repository and insert to the repository, and write a comment about the change also. It should be a sync instance between the power bi and power desktop when we edit a report in power BI service.
Niels Andries commented
Nice feature, but will this be available for live connections to Analysis services cubes also?
Peter Wickwire commented
You provided the WHAT IF parameter in the August 2017 release. It looks great. HOWEVER, it is not supported by SQL Analysis Services cubes (OLAP or TABULAR). PLEASE update this feature to work in Reports that are hitting SSAS data sources
When will this be available?
When will this be made available? Waiting..
When will this be available?
Samir Mammadov commented
Hi. Is it possible to include "What if" analysis tool in future versions of Power BI? I think it will be great present for Power BI guys.
arvind yadav commented
Hi Will Thompson,
Its great to see what if analysis in Power BI . Please Resolved "What If" analysis query.
What about passing a parameter into an R visual?
I agree with others that an input box that can be used in DAX formulas would be the best and most versatile solution, but hopefully they make they adjust the slicer to act in a similar way.
Niek Verhoef commented
A free form input box would be best for all situations, where users can enter a number (example value: 1, 5.55, 2000, 24000), and use this number within an expression (units * example value = new sales)
Please provide this feature as this will be great help for analyzing data.
Bill Ritzel commented
The date slider is already there - just give us a version that returns a number between two specified values, with defaults of 0 and 100 for percentages, and I believe that it would cover a lot of us.
John Merchant commented
This is great news. I built a pricing model where users can change the price for each product (50-60 products) and see the impact to sales using a filter / disconnected parameter table. The issue is that there are 50-60 parameter tables within the data model, and our sales force mentioned the report filters are not intuitive. A free form input box would be ideal for my situation, where users can enter a number (example value: 1000,2000,3000), and use this number within an expression (units * example value = new sales); but the method described in this post should help as well. I am excited to see how this new feature can help improve the data model and user interface of my report. Thank you!
Alan Strange commented
Brilliant! I work for an insurance company so I'd like to be able to model eg what if premium were x% more, or claims y% less. And what would be great would be to be able to see what would be the effect of an excess of £z (or adding a fixed amount to an existing excess), meaning reducing each claim by a set amount (ideally bound by a minimum value - ie minimum adjusted value of £0).
This is HUGE especially from a competitive perspective. Looking forward to the release!
It would be cool if you could add an additional row for a fact table. For instance, we use power bi for monitoring portfolio exposure, and in order to "what-if we add or remove position X and Y" we need to reload the entire model. Another ting would be to change values of current rows.