Dynamics GP Power BI Content Pack Now Available!
Hello everyone!
With the release of Microsoft Dynamics GP 2018, we have also included a new Content Pack for Power BI. Click below to download it:
[View:/cfs-file/__key/communityserver-blogs-components-weblogfiles/00-00-00-05-36/DynamicsGPContentPack.zip]
The Power BI Content Pack features sample reports for Financial, Sales, Purchasing and Inventory data. Each report utilizes relationships built between GP tables, and various Filters that can be used to display the information is that important to you. You can also review the included Calculated Columns as examples for including calculations on your Power BI reports such as Net Debit/Credit, Profit and item Sales amounts.
Upon launching the Content Pack file in the Power BI Desktop application, you will be prompted for your OData Feed URL.
Please refer to the following blog article for information regarding installing and configuring the Dynamics GP OData service for use with the Power BI Desktop application:
The Content Pack is meant to demonstrate the possibilities of Power BI and is a good point of reference for designing your own Power BI reports for Dynamics GP 2018.
Enjoy!
Comments
-
Dynamics GP Power BI Content Pack Now Available!Are these files still available? The link seems dead, Can anyone share the file?
-
Echo what Béat mentioned. Would be more useful to have this Content pack available for regular SQL connections. It would also make it easier to prepare reports and demonstrate Power BI to prospective GP clients (it's all about data visualization now and would be a good feature to show off and keep GP updated with the times)...
-
Thank you Jeff, But when is Microsoft going to wake up and realize that no one is using ODATA with GP ??? I haven't met yet a single client in my entire GP consulting carriere with ODATA setup to use with GP.. I tried (painfully) to convert the GP Content Pack for Power BI to regular OLEDB or ODBC connection for all the reports, but only partially succeeded, because all the queries have to be rewritten as the ODATA strings are slightly different from queries you would use when going the route of direct SQL connection. When you change the connection from ODATA to SQL, none of the queries are working anymore because of the way they are built. Microsoft would have much more success with this Content pack if it would make it available for regular SQL connections.
-
-
Can you provide any guidance on converting the OData to SQL for this content pack? We intend on using the PowerBI On-Premises Data Gateway, don't have OData service setup, and I believe it would be best to convert this to SQL.
-
Does this mean the client is entitled to Power BI in this context without purchasing any other Power BI licenses?
*This post is locked for comments