Microsoft Dynamics AX 2012 R2
Now available for Microsoft Dynamics AX 2012 R2, the Code Comparison tool includes support for SSRS Report design nodes. These enhancements were made to address some of the feedback we’ve received from our development community. Instead of flat text comparison of the RDL, we now offer an integrated experience with tree node management to navigate the XML design definitions. Comparing report designs now provides a structured view of the report model separating the datasets, parameters, and design definitions into distinct sections. These improvements dramatically reduce the complexity of comparing SSRS Report design definitions across layers.
Note: These enhancements reside in the X++ system classes and do NOT require a service restarts to begin using in your deployments.
Where to get the tool enhancements for Microsoft Dynamics AX 2012 R2?
Hot fix Available here: http://hotfix.partners.extranet.microsoft.com/search.aspx?search=2894015
Does the tool enhancement include support for merging across layers?
Unfortunately, this hotfix does NOT include support for merging changes across layers.
Simple example – I’ve made a basic customization to the AlertsetupReport. This is a basic tabular Auto Design report that includes a single table in the body. I’ve done nothing more than update the DisplayWidth property of the Enabled column. Now, I’ll use the Code Comparison tool to compare the report node before applying the hotfix against the results after applying the hotfix using the same report.
Steps to access the Code Comparison tool:
- Select a SSRS report design node in the AOT under the SSRS\Reports folder
- Right click the report node and select Compare
- Click the Compare button
Results before hot fix applied:
The engine applied a flat text comparison of the XML based report design definitions. This approach makes comparing report models when major changes have been made to the report design extremely difficult to decipher.
Results after hot fix applied:
The Code Comparison tool now reads the RDL file into an XML document and performs a node level comparison. This offers a more granular breakdown of the report design filtering out all of the unaffected tags by surfacing only those nodes that have been modified and their parents.