Microsoft has always been great at building and delivering world class robust commercial software, but it hasn’t always been great at listening to specific customer concerns about gaps in the software. All this has changed now, and Microsoft now has a clearly defined process to ask its customers what is important to them, and then prioritising these things for the new releases. Power BI (and Excel) both have specific user voice websites where anyone can submit their ideas for improvement. In the case of Power BI (at least), the team DOES read the feedback and acts on the best ideas.
It works like this –
- Any Power BI user can post an idea in the Power BI ideas forum – ideas.powerbi.com.
- The other users can then vote for the idea if they also find it useful.
- The ideas that get large number of votes are considered by Microsoft for implementation.
- Even the ideas that don’t get a large number of votes still get consideration. More on that later.
Many ideas have been posted in the last 3 years and many of them have been implemented. Whenever I find that adding or enhancing a feature would useful, first go to ideas.powerbi.com and search for an idea that someone else has already created. If I can’t find a similar idea already, I post a new idea. I also generally look at the other ideas regularly and vote for them if I also find them useful.
Below are the ideas that I have created that I think should be implemented. Yes, you got it! Your vote can make a difference to these changes being implemented. Please take a look at these ideas and importantly please VOTE for them if you agree in their merit.
Conditional formatted measures using SWITCH
A current limitation in Power BI SWITCH measures is that they must have a single format. It is currently not possible to conditionally format the measure result based on any criteria – it is one single format only.
There are valid use cases where you may want to change the format of the SWITCH measure depending on the result.
IntelliSense Should Use Best Practice Column and Measure Naming Conventions
There is a clearly defined and accepted best practice for referencing columns and measures in the DAX language.
1. Column names should ALWAYS reference the table name.
2. Measures should NEVER reference the table name.
This is a fundamental concept accepted by everyone with knowledge of the DAX language (everyone I know anyway).
IntelliSense in the DAX sometimes follows this convention and sometimes it does not. I have created a short video (40 seconds) showing 3 examples. https://youtu.be/CvaRhKrnHRk It seems to fail when ever the column name and the table name have the same name, such as MyName[MyName of Col].
There are other places where column names are appended to measure names too, such as inside Quick Measures, and I have also seen Column Names used without prepending the table name.
This is an issue, and fixing IntelliSense so it always follows the best practice would enhance user experience.
Improve Relationship Drag and Drop Experience
In Power Pivot for Excel, dragging and dropping columns to create relationships works like this.
1. Click and drag source column.
2. Hover over destination table.
3. The receiving column on the destination table is highlighted to indicate which column will receive the join.
In Power BI Desktop, item 3 above is missing. It makes it ambiguous how the join will be made (and a poor user experience). Adding a visual confirmation to the user which column will receive the join during drag and drop would be helpful.
Also, if you click or hover on the relationship, make the tables scroll so the user can see where the join is.
Read Only Access to Relationship View in Thin Workbooks
My definition of a thin workbook is when you connect Power BI to a tabular server. This can be SSAS Tabular or the Power BI Service (golden dataset as covered here https://exceleratorbi.com.au/new-power-bi-reports-golden-dataset/).
When you use Power BI Desktop as a thin workbook, you cannot see the relationships view or the data view. While this makes sense (they are not editable), it means that it is very difficult for someone to write local measures. It is not possible to accurately write a local measure unless the relationships between the tables are visible.
Please add the relationships view so the end user can see the table structure and assist in writing measures.
Link a Bookmark to Image with Spotlight Enabled
I would like to create a bookmark with a visual in spotlight mode AND provide a button to return to regular mode. Currently (as far as I can determine) I can place a visual in Spotlight mode and then add a bookmark for this. I can then link this “spotlight bookmark” to an image for the user to click. But then when Spotlight mode is on, there is no ability to click on an image/button linked to another bookmark that returns me to another view. I want to be able to click on a button (or image) to display a bookmark with a Spotlight highlight, and then somehow get back to the previous view or a specific bookmark.
This is currently not possible unless you do it directly in the bookmark pane. I would like to click on an image on the screen linked to Bookmark (or some other solution that is intuitive).
Mapping Visuals Should Send All Location Data to the Bing Service
If I add a list of State codes to the location card on a map, the results will normally not be accurate. The States selected could be from anywhere in the world – if you don’t add the country details first, you get inconsistent results. If I have the following Columns in my data model: Address, State, Post Code, Country, and assuming they are all categorised correctly using Data Category, then these columns should be sent to the Bing Service regardless if they are added to the visual or not. So if I put Address onto the map, I would like the full set of categorised columns that exist in my table to be sent to the Bing Service even though State, Post Code and Country are not actually placed in the visual.
This would greatly increase the usability and accuracy of the mapping visuals.
DAX Query Language Visual
There is a big value in creating a visual that can display the results of a DAX query.
This would give report writers very granular control to display records without having to use a table visual and a measure that triggers the display of the correct records.
When Cross Filter is Off, Chart Should Not Be Clickable
Currently when you turn off Edit Interactions for an object such as a column or bar chart, that chart will stop filtering any other items on the canvas. However when you click on one of the bars or columns, you can still select the item though it doesn’t do anything. This is confusing to the report users.
Use Power BI Desktop as a Local Server on a PC
There is an “Analyze in Excel” feature in the Power BI Service and I would like to see the same for Power BI Desktop.
There is already a “Connect to Data” button that connects to the service. You could enhance this to include a button that connects to a local instance of Power BI Desktop running on the PC.
Extend “Include In Report Refresh” Further
It would be great to allow the user to set parameters and events to control when a table is refreshed.
This will allow granular management of refreshing when a user needs to partially refresh a workbook.
The Small Stuff List (The SS List)
If there is a way to request small stuff that needs to be fixed, it can be reviewed by developers and if they agree, they can just fix the small stuff when working in the bigger stuff (assuming it is easy) or they can recommend it be promoted to an idea if it really is big stuff.
If the ideas are categorised into areas, the developers can easily find their own stuff, and also a way to remove things from the list once they are done.
Recently when I was in Seattle at the MVP Summit, I got chatting to one of the many great Microsoft Developers (Kay Unkroth). Kay told me that people DO look at ALL of the ideas regardless of how many votes it receives. What happens, when Microsoft is about to do some work in a particular area of the software, is that the team goes to ideas.powerbi.com and finds all the ideas that are relevant to that part of the software. It makes sense to bundle up all the small stuff at the same time as you are about to work on a section of the code base. This is a long way around saying that you should create ideas for everything you want to see developed.
If you find any or all of these ideas useful, please vote for them … Your Vote Makes a Difference! And how about just browsing the top ideas and vote up the other ideas you think look worthwhile.