This is on in our plans for Power BI Desktop! Stay tuned :-)
Hi everyone. There are some really interesting ideas in this thread, thanks for your vocal support about it! We’ll consider it for the future along with other suggestions and plans. Thanks!
Don't think it was covered in the 3 items posted in this request, but I would love to have an API to create and modify dashboard reports, visuals, so I could have a base PBIX and then scripted modifications to add/remove elements before sending out to a customer.
We’re pleased to announce that in the May release of Power BI Desktop you can now define incremental refresh policies for your models.
At present these only apply once the model is published to a Premium workspace in the Power BI service; we’ll be bringing it to all Pro users in the future.
You can read more about it in our blog here: https://powerbi.microsoft.com/en-us/blog/power-bi-desktop-may-2018-feature-summary/#incrementalRefresh
We’re going to leave this idea open for now, so please give us your feedback while we’re in this preview phase!
When hovering over a relationship line, also highlight both the tables, as well as the joined column in each table (scrolling/zooming the window where necessary)
When hoving over a table, highlight ALL its relationship lines AND the joined tables AND the joined columns in the respective tables.
When taking over someone else's complex model, this would be a life saver.
Checking with Will Thompson and moving status to backlog
> Imagine needing to create 50 measures: currently you need to press "Create new measure" and edit the formula each one at a time. With this proposed design you can create them once in PowerBI OR quickly in a table in Excel, and then simply paste them all into the existing PBIX or any other going forward.
The ability to paste a whole bunch of measures all into one window (the ability to specify the home table where they will reside would be nice too) would be a KILLER feature for me!!!
Amazing mockup by the way OP.
Ruth points out here that it appears that the physical column names (as opposed to an id or guid) are what's used to bind the model to visuals: https://www.youtube.com/watch?v=JJryD2dXVVw
Changing this to instead bind on an id (and store the textual name elsewhere) seems like it could be an incredibly difficult change as it would be very deep in the core of Power BI. But what about this approach.....as we know, we can already change table and column names in the Power BI user interface and it works just fine. All that implementation works perfectly well. So, rather than making deep fundamental changes to bind on id's, why not just provide a simple API **to the very same code that the existing Power BI user interface calls today**? Would everything not then work exactly as it does today when a user manually calls it by right clicking and doing a rename?
var powerBI = new PowerBIApplication();
var myModel = powerBI.OpenModel("c:\users\Jimbo\Desktop\AwesomeModel.pbix");
myModel.RenameColumn("TableName", "OldColumnName", "NewColumnName");
I can't think of a good reason why that wouldn't work.....am I overlooking something?
sisense lets their users do it:
This would be a very informative enhancement, and I'd think fairly easy to implement. All of these relations already exist in metadata, and code already exists for mouseover events and highlighting the corresponding fields and connectors, so it should just need an on_load modification for the first request, and the addition of a table mouseover event whose implementation is very similar to the connector mouseover.
Currently, you can can kind of do extremely simple interactions like so:
But it is very obscure and lacks full control.