Power BI User on 20 Aug 2015 23:29:33
What about adding input fields to the dashboard widgets. Kind of like the text field but it is enabled for user input. This input field can be used in new column and new measure fields so that once the dashboard is set up the user can easily (without filtering) explore the data by entering different values such as if you had an input box for unit price. Then if you change it all the charts of total sales, revenue, etc. Will update to reflect what would happen if you increase the price by 10%. This will enable people to quickly and easily interrogate the data
Administrator on 21 Oct 2022 02:41:16
Thanks for the feedback! This is something we'd like to get to in the future but don't have any plans for at the moment. We suggest checking out the visual Text filter on AppSource in the interim.
- Comments (253)
- Merged Idea (7)
RE: input fields
Absolute must have. Needed in so many use cases to demonstrate what if scenarios and many other criteria where the user needs to interact with the data by modifying a control variable.
RE: input fields
This would actually be super helpful from a presentation point of view, so for instance if someone in public health sector is presenting current spending and associated economic benefits for a specific intervention, they can change the spending on the fly and demonstrate the impact.
Would be really nice to have this!
RE: input fields
A must have. This feature is available in many of the similar tools. Also, this can't be achieved by Parameters in PBI. Not even with the pre populated numbers table that can be used as a input field --> In this case, the measure can use it for very simple referencing but not for medium to complex calculations.
RE: input fields
This would be great if this feature is added. Cuurent What if parameter has limitations
RE: input fields
This an a variety of other data entry options are already available in the Acterys (https://www.acterys.com) visuals: https://appsource.microsoft.com/en-us/?search=acterys
RE: input fields
This would be a very useful feature. Current What-If Analysis has some serious limitations (i.e. cannot enter any number, you need to pre-define maximum and minimum range, plus at some point, it is losing its accuracy and is rounding the numbers). Also, input fields could accept non-numeric fields, which will also be useful for the analysis/filters. Image having a possibility to include user's input in a measure - a dream come true!
RE: input fields
A basic feature for Reporting Services among other tools, and they don´t have any idea of implementation. What a shame.
RE: input fields
how is this different than the whatif-parameters feature already in PBI?
RE: input fields
I was just looking at how to implement this feature like paginated reports, it's very disappointing that it is not available. Some of our PowerBI reports would be much simpler if, we could guarantee that we were only looking at the required data across generally unrelated fact tables. Instead of trying to make them fit into a difficult schema.
this would be better if the user were prompted, this is how we've organised a lot of paginated reports and makes it very easy to manage tablixs, when you can guarantee that you are only concerned with the right data.
Further more the parameter use seems to want to apply to the dataset in powerbi Services. this is probably not the expected outcome for alot of people wanting a prompt as PERSON A will want a different set of data to PERSON B.
In saying that, parameters for modifyng locations and servers is very useful. but maybe what people are asking for here is the difference between a variable and a parameter, but you also want a variable to influence a parameter and an import/direct query just like paginated reports. I would love to be able to write a direct query like select * from table where date > @userdate.
RE: input fields
Where a report is created, that requires additional input and action to complete tasks, a way to comment of status within the report view associated to the item being reported on would improve the service, without having to go back to the source data. If this were the case, then primary solution would be to use source data and ignore powerbi.