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
Really need this to work out. Most clients require a dynamic input field to be able to simulate analysis . It is difficult for them to go to edit queries , change the value, refresh the dashboard etc. Moreover, if I try to use parameters, they only work on measures and not on columns, so there is no way I can simulate on a line item basis.
Please upgrade to this feature.
RE: input fields
great idea
RE: input fields
Much needed. Without this , we are facing hard time with Power BI Reports.
RE: input fields
What is the value of Power BI parameters if the user can't enter them?
RE: input fields
I agree this would be a great enhancement. We see thousands of clients and it would be useful for our staff to enter the client id and drill down into the data.
RE: input fields
Please add this feature. It is a very common request. Thanks.
RE: input fields
For a retail business, this is a common and frequent ask from users...
RE: input fields
This would move PowerBI to a new level and allow for better use of the visual page (i.e. being able to type in a year of interest rather than selecting it from a slicer would reduce the space required)
RE: input fields
This ticket has been out there for 3 years and it's not even off the backlog? We're considering switching back to Tableau because of this as it's a basic expectation of our users.
RE: input fields
Surprised this doesn't exist already. Should be your Number 1 Priority moving forward