How can we improve Power BI?

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.

1,239 votes
Sign in
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Rajnish SinhaRajnish Sinha shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      • arvind yadavarvind yadav commented  ·   ·  Flag as inappropriate

        Hi Will Thompson,

        Its great to see what if analysis in Power BI . Please Resolved "What If" analysis query.

      • MattMatt commented  ·   ·  Flag as inappropriate

        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 VerhoefNiek Verhoef commented  ·   ·  Flag as inappropriate

        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)

      • Bill RitzelBill Ritzel commented  ·   ·  Flag as inappropriate

        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 MerchantJohn Merchant commented  ·   ·  Flag as inappropriate

        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 StrangeAlan Strange commented  ·   ·  Flag as inappropriate

        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).

      • TylerTyler commented  ·   ·  Flag as inappropriate

        This is HUGE especially from a competitive perspective. Looking forward to the release!

      • MadsBoeghMadsBoegh commented  ·   ·  Flag as inappropriate

        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.

      • BoubertBoubert commented  ·   ·  Flag as inappropriate

        Great, great news!! Tableau have this feature since a long time and it is very used by users. It is a little feature but with a strong impact.

      • Neville de SousaNeville de Sousa commented  ·   ·  Flag as inappropriate

        It would be great if the what-if analysis will be able to handle modifying discrete values.


        I work in the logistics industry and look at turnaround time (estimated and actual: arrival to complete load) for ships coming to load at our terminal. As such we look at the overall turnaround for x number of vessels over a particular future date window.

        It would be great to be able to modify the estimated arrival and complete load for 1(or multiple) ship(s), which then updates the turnaround metric, to gauge the impact to the overall turnaround. This will have the added benefit of smoothing out load on terminal assets.

      • Anonymous commented  ·   ·  Flag as inappropriate

        So if I understand this thread, a numeric range slicer control is being reviewed for possible future inclusion in Power BI, but there is no What If solution currently available? Am I right?

      • Duncan PrydeDuncan Pryde commented  ·   ·  Flag as inappropriate

        Just as an aside, I've been trying to use the numeric range slicer for exactly this purpose, but run into an issue as described here: and in more detail here:

        I can get around it by removing the slider and keeping the entry boxes, which may work for may of the cases here.

        In my scenario, we wanted to create an upper and lower bound for what-if analysis, so the range slicer is perfect for that purpose, but being able to enter a single value would be very useful.

      • robrob commented  ·   ·  Flag as inappropriate

        What if analysis would close the gap on Tableau and increase adoption

      ← Previous 1 3 4

      Feedback and Knowledge Base

      Ready to get started?

      Try new features of Power BI today by signing up and learn more about our powerful suite of apps.