We, BI professionals, sometimes take for granted that we can access the database of an ERP system quite easily, especially one that is made by Microsoft. However, the live Dynamics (365) AX database cannot be assessed directly currently.
The diagram above shows that the Primary AX DB is copied into the Secondary AX DB for reporting purposes. However, the Primary and Secondary DB cannot be accessed directly in the Live system. The Entity Store, however, can be accessed either via OData feeds or by synching with an Azure Database.
Creating a Data Entity
Creating a Data Entity is easy. Start by logging into your VM. Start Visual Studio 2015 as an Administrator.
Well, hello. It has been more than three years since my last blog, since then I have been really busy at work and have a baby in the meantime.
That being said, I wonder how much joy you guys have with playing with MR.
I have been using Dynamics AX and MR for more than 3 years now and I am still able to learn new things. One of them is that MR is able to use the organizational hierarchies of Dynamics AX as the reporting tree.
For those who are clueless, in your organisation, you can define the organisational hierarchies of not just the standard organisation but for all your financial dimensions. The idea is that when you select an organisational hierarchy as the reporting tree, you do not need to create it from scratch. Furthermore, when the hierarchy changes in AX (I dropped the word “organizational” as it just makes typing too long), MR is able to reflect that based on the period selected for the report. I thought that was pretty cool.
What happens when you want to use the hierarchy as a filter in the column definition?
Terry: why in blazers would anyone want to do that?
Well, it so happened that I had a customer who needed to do just that.
Imagine the need to have different columns represent the amounts not at leaf level, but at a middle hierarchy level. Sure, you can filter on dimensions and manually create it, but there is no need to re-invent the wheel.