
Are there any known differences between the way that Power Query in Excel collects data from D365 and the way that Power Query in Power BI collects data from D365.
I am trying to create a set of queries in Power Query, in Excel, that will extract and combine data from a number of D365 tables and load a single table to the Excel ‘front end’. The starting point for my Power Query work is FetchXML queries that I convert to M code using Power Query (M) Builder in XrmToolBox. Power Query (M) Code is a fantastic product which produces M code that works perfectly in Power Query in Power BI.
When I run the M code in Power Query in Excel not all of the D365 records come back. The same M code in Power Query in Power BI pulls all the expected records back. The exact same code does what it should in Power BI but not in Excel. This happens for several tables. So far as I can tell it’s always the same records that are missing from the Excel version. I have scoured the tables looking for something about the missing records which might determine why they are being missed while the others aren’t, but without success.
I’m on Office 365 with automatic updates which I assume means that my Excel environment is as up to date as it can be. My Windows 10 environment is also on automatic updates so that is up to date as well. I was under the impression that the Power Query environments in Excel and Power BI were the same. They are certainly similar but there’s obviously at least one difference under the bonnet.
Thanks
Ian
It would be good for a support engineer to look at the power query that is being used in excel to retrieve data from Dynamics. I would suggest opening ticket for this for Mcirosoft SE to analyze.
here is an article that talks about power queries in excel
powerobjects.com/.../analyze-that-data-with-microsoft-power-query-for-excel