Power BI Dashboards Built on D365F&O AxDB (For On-Prem Environments)

-

 


This blog post is a showcase for Microsoft Power BI Dashboards/Reports developed for Power BI Reporting Server. Meaning, the dashboards/reports have been built using the AxDB database and not AxDW (referring to the Entity store in D365F&O). The dashboards/reports are:

  1. Asset Master.
  2. Customer Statement.
  3. Employee Loans.
  4. Government Transactions.
  5. Item Requirements.
  6. Posted Project Transactions.
  7. Project Budget.
  8. Project Master.
  9. Project WBS.
  10. Purchase Agreement.
  11. Purchase Order.
  12. Purchase Requisition.
  13. Trial Balance.
  14. Vendor Statement.


 1. Asset Master

 

2. Customer Statement

 

 3. Employee Loans

 


4. Government Transactions


5. Item Requirements

 

 

6. Posted Project Transactions

 


7. Project Budget

 

8. Project Master

 

9. Project WBS


10 Purchase Agreement

 

11. Purchase Order

 



12. Purchase Requisition

 

13. Trial Balance

 

14. Vendor Statement



Comments

Post a Comment

Popular posts from this blog

How to Deploy a Package from DEV to UAT using LCS

-
Image
Scenario: Suppose you have been tasked to create a deployment package and deploy it to a UAT environment. For a beginner, who has never done a deployment before, the task might seem overwhelming. Regardless, getting it done is what this blog post is for. Consider you are on a cloud-hosted DEV environment for Microsoft Dynamics 365 Finance and Operations. You or some developer has written x++ code, or perhaps created custom entities or it can be any type of customization for D365 FO. Your customizations have been tested and approved to be deployed to UAT (User Acceptance Test) environment. Using Lifecycle Services (LCS) we will deploy your customizations to a UAT environment. As you might be familiar with or know, there are a few different approaches to deploying customization to an environment. This blog post solely covers deployment through LCS.   Prerequisites: To successfully perform the process, you will need: Access to DEV environment, i.e. where your customizations lie. Adm...
Read more

How to Deploy a Package from UAT to PROD using LCS

-
Image
  Scenario: Continuing onward from the previous blog. How to Deploy a Package from DEV to UAT using LCS Your customizations have been successfully deployed to a UAT (sandbox) environment. Functionals and/or users have extensively tested and verified the customization on the UAT environment. You have been given go-ahead and now you need to carry those customizations from UAT environment to production environment. All right then, let’s jump right into it! Prerequisites: To successfully perform the process, you will need: Admin creds or project security role of "Project owner" on LCS. A successfully completed deployment on a UAT (sandbox) environment. Process: Step 1: Mark an application deployable package from a sandbox environment as a release candidate for a production environment. Step 2: Schedule the release candidate on a production environment. Step 1: Mark an application deployable package from a sandbox environment as a release candidate for a production environment. ...
Read more