Power Query Builder updated – now supports FetchXML to get your Dynamics 365 Views into Power BI

The latest version of the Power Query (M) Builder for the XrmToolBox has been updated and it now supports FetchXML.

Used for creating data models for Dynamics 365 in Power BI, the Power Query (M) Builder accelerates the development of the Power Query (M) code, that retrieves the records, change column names and their data types. The tool automates the field selection and the initial data transformation steps that normally has to be done manually.

With the latest version supporting FetchXML, the tool can now import the labels for option sets and lookup fields directly. That means creating additional transformations or DAX formulas are no longer needed just to show the proper label of an option set.

Here’s the latest video showing the updated features.

For more information and credits to everyone involved in this project, please check out the Power Query Builder page for full details. That page will also be continually updated with the latest updates on the tool.

Enjoy. As always, please sign up for my newsletter or follow me on Twitter 

3 thoughts on “Power Query Builder updated – now supports FetchXML to get your Dynamics 365 Views into Power BI

  1. Thanks a lot for this tool, very interesting to see this type of m script generation tools!
    With regards to accessing dynamics data,

    What is now the best/most optimal way to get dynamics data into power BI?
    I was using the odata link in Power BI but that was very slow so went for the data export service using an azure sql database.

    But looking now at this fetchXML access, what would you feel is the most optimal tool to use to create reports for CRM?

    • Depends on the amount of records and what you are doing. Using the FetchXML as above is definitely the easiest way to create a data model and significantly faster than working with the OData. But if you count your records in the hundreds of thousands, then the Data Export Service might be a better option.

  2. Very cool tool! Would we still need to create security roles in Power BI for the intended end user or will the filter in the XML take care of it? For example: If Joe pulls up a report in Power BI that uses the data from My Accounts, will it only show his accounts in the Power BI report?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s