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 25 Jul 2020 23:46:00
Hi everyone. This is something we'd like to get to in the future but don't have any plans for at the moment.
- Comments (227)
RE: input fields
Oh aye, this would be dead good!
RE: input fields
Yes Please!
I am working on dashboards to report on the learning progress for Neural Networks in Azure ML and it would be very handy to have userform level input fields.
RE: input fields
Any idea when this will be implemented?
RE: input fields
Indeed would be super useful for what-if analysis!
RE: input fields
Very Important and much needed functionality. Any idea if in near future we will hear about this
RE: input fields
Here at the company that I work in, we need this resource a lot.
Extremely necessary
RE: input fields
Yes this is absolutely required! This is where PowerBI falls short of Qlik Sense, Qlik View, and Tableau.
RE: input fields
Never mind text fields, a simple numeric input field would absolutely amazing... Where the report user can pick whatever cut-off or value they want....
I've been doing all these work arounds by defining different value ranges then putting them in different slicers... Which is my attempt to predict what different cutoffs or values the user would likely pick...
Adding this ability would enhance the effectiveness of the "what if" scenario analysis/data exploratory tool that can be done in Power BI Reports
RE: input fields
We need this feature if we want to address the problem of slicers not working across multiple reports.
RE: input fields
Absolutely endorsing this one.