Power BI Designer saves a local PBIX file, which can be a file to export data and data model – in other words, it’s a format that contains a complete semantic model. All the applications that today export data in several formats (CSV, Excel, XML), might provide a richer semantic model exporting a PBIX file.

Many ISV/SI that have OLTP and other applications that stores data in some database, usually struggle to offer a compelling BI story to their customers. The smaller they are, the more they feel this pressure because probably the effort they can put in their custom software is minimal.

Today these ISV/SI integrate their solution with external vendor technologies (QlikView is a common choice here). However, the cost of such a solution for the end user is not always appealing, and for this reason the MS partner ecosystem always look for components (charts and pivot tables) to integrate in their solutions.

Providing them an easy and inexpensive way to produce PBIX files “ready to use” straight from their product/solution would provide several benefits:

- Customers would have something ready to be uploaded to Power BI service

- ISV/SI would be able to provide a BI solution integrated with MS ecosystem

- ISV/SI can implement solutions like “send a PBIX file via mail every week to all the agents including only the data of their prospects/customers” - Today they already do that using the .CUB format, which can be consumed by both Excel and custom applications

- Microsoft would increase the number of Power BI users very quickly - Small ISV/SI would be able to implement such integration very fast

What I propose to do is, in descending order of importance:

1) Support Power BI Designer as a local engine with an API that can be used by anyone and officially support local connections by other programs (starting from Excel)

- The API should provide the ability to create a data model and to populate it with data by just using API, without any manual interaction

- Providing the ability to connect from other clients (today it is possible but not officially supported) would increase the adoption.

2) Document and “open” the PBIX file, so that it can be generated by anyone

- I think that this is easy for the data model, but not for the data.

- But without the data, this model would be not so useful, requiring a manual refresh to be populated.

3) Open source the Power BI Designer

- Not really a priority in my opinion, but if the first two wouldn’t be possible, this one could be ok
Under Review
Ideas Administrator

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!



So PBIX is clearly some sort extension of Office file formats, it is surprising that it is not documented.


We need to convert hundreds (or thousands if counting multiple clients) of legacy BI reports into Power BI, but this looks impossible without designer API or make .pbix in XML format.


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.


Come in, I want to be able to do my Prototyping in Power bi then move my Model to an enterprise Tabular Server. Why have you made Power bi sich a closed system?


2015 and still under review?


Great idea.
When using the "Import" option, I would like to be able to publish the model to my on-prem SSAS Tabular Server while the metadata is being uploaded to the cloud.


Waiting eagerly for this


We need to be able to automate report creation. Make this happen! :)


We can surely benefit from this request


This would be an amazing feature for partners and users alike. I'd be cool if it was the ability to import templates into the same pbix file, or actual pbix files.