PowerQueryBuilder 1.2019.423.8
dotnet add package PowerQueryBuilder --version 1.2019.423.8
NuGet\Install-Package PowerQueryBuilder -Version 1.2019.423.8
<PackageReference Include="PowerQueryBuilder" Version="1.2019.423.8" />
paket add PowerQueryBuilder --version 1.2019.423.8
#r "nuget: PowerQueryBuilder, 1.2019.423.8"
// Install PowerQueryBuilder as a Cake Addin #addin nuget:?package=PowerQueryBuilder&version=1.2019.423.8 // Install PowerQueryBuilder as a Cake Tool #tool nuget:?package=PowerQueryBuilder&version=1.2019.423.8
Create Power Query (M) scripts for Dynamics 365 and Power BI
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net452 is compatible. net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
-
- XrmToolBox (>= 1.2017.3.14)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
1.2019.423.8 | 96,894 | 4/23/2019 |
1.2018.1014.5 | 13,060 | 10/14/2018 |
1.2018.7.20 | 9,611 | 7/19/2018 |
1.2018.7.7 | 3,329 | 7/7/2018 |
1.2018.7.5 | 1,516 | 7/5/2018 |
1.2018.6.25 | 3,347 | 6/25/2018 |
1.2018.6.15 | 3,037 | 6/15/2018 |
1.2018.6.4 | 1,277 | 6/14/2018 |
20190423
-Inclusion of all entities
-Errors when generating queries based on custom FetchXML with entities not available in Advanced Find has been fixed. It is now possible to pass any query generated in the FetchXML Builder to the Power Query Builder, either manually or using the integration.
-RelativePath in web.content calls
We have added the use of RelativePath to the web.content calls. Whereas the current setup would create a connection for each entity in the Power BI service, using RelativePath will reduce it to only one connection that needs to be maintained for refreshes etc.
Big thanks to hanksteen on GitHub for the suggestion. https://github.com/ITLec/PowerQueryBuilder/issues/26
-Date formatting
The current transformations for custom date and time fields, formatted as date only, would generate errors. We have changed all the date fields to only retrieve the formatted value via the FetchXML, which fixes this error. The added benefit is that all dates and times are now retrieved in the users local time zone rather than UTC. Data still includes time zone details.
20181014
-Add Linked Entity
-Link with FetchXmlBuilder
20180720
-FetchXml feature has been added.