BI Report Development for Microsoft Dynamics AX 2012 Case Study
The client is a multidisciplinary engineering and technical services consulting company servicing clients in the Mining, Oil & Gas, Infrastructure and Pulp & Paper sectors.
They deliver innovative, practical solutions that fulfill project needs and fit within the reality of their client’s budgets.
The client recently implemented Microsoft Dynamics AX 2012. They wanted to develop business intelligence reports for AX to be made available in their respective modules in the AX as well as published to SharePoint.
They were originally planning on developing the reports in AX using X++ which is expensive and is not natively supported in AX and SharePoint. The X++ to AX/SharePoint would also add to the maintenance overhead.
The client was looking for a cost-effective way to develop these reports for Microsoft Dynamics AX 2012 and better integrate their reporting with their SharePoint infrastructure.
They also needed some guidance on security level of the reports when published in AX and SharePoint.
The client was also facing a looming deadline and needed to speed up report development.
- Requirements gathering.
- Report development.
- Report testing.
- Report walkthrough.
- Report deployment.
How Optimus Helped
The Optimus team discussed the challenges with the client team and suggested to leverage SQL Server Reporting Services (SSRS) to develop the reports. SRSS comes with SQL Server as well and is compatible with both AX and SharePoint.
We worked with the client team to setup reporting infrastructure. And we walked the client team through the report development process and the various templates they would use.
We then interviewed end users and created report design and requirements documents. Once the report requirements and design documents were finalized, the Optimus team started the development of the report.
Meanwhile the testing team held a session on test scenarios with the client and began developing test cases. After the report development, Optimus team used the test cases to validate the report and perform bug fixes, if necessary.
We then walked through the reports with end users using the test scenarios as reference. Once the report was signed off, it was published to AX and or SharePoint as required.
Finally, change requests were handled separately after deployment.