{"id":5211,"date":"2019-06-11T11:07:23","date_gmt":"2019-06-11T11:07:23","guid":{"rendered":"https:\/\/patrickmouwen.com\/?p=5211"},"modified":"2024-01-26T11:55:44","modified_gmt":"2024-01-26T11:55:44","slug":"d365fo-identify-config-differences-across-environments","status":"publish","type":"post","link":"https:\/\/patrickmouwen.com\/functional\/d365fo-identify-config-differences-across-environments\/","title":{"rendered":"Identify Configuration differences across D365 F&O environments"},"content":{"rendered":"
\n

We’ve all seen it many times in our projects.. Being under pressure to close these last P1 and P2 bugs by making some quick config changes in UAT, we forget to keep a record of what we did and to bring this into our Golden Config environment. And then, after cutover to Production, our users are confronted with the same issues as before.. How great would it be if we can prevent this with an extra ‘lock on the door’?<\/p>\n

Dynamics Versions<\/h2>\n

The method of comparing configuration between D365FO environments as described below is utilizing D365 Data Management capabilities. If you’re still working with AX2012 you’d also be able to apply most of it with DIXF.<\/p>\n

How it’s done<\/h2>\n
\n

STEP 1:<\/strong> Represent your critical configuration areas in a D365 Data Template<\/span><\/p>\n

\n

We all know our ‘sensitive’ setup areas which can give real trouble when not 100% identical in the various D365FO environments – Areas such as Financial dimension values, Tax setup and module parameters. To have a good starting point for your Config ‘lock on the door’, ensure to represent these areas by Data Entities in a D365 Data Template<\/a> which you could for example name “D365_Setup_Compare”:\"D365FO<\/a><\/p>\n

Export this template into a SharePoint library for easy re-use and version control.<\/p>\n

\n

STEP 2:<\/strong> Create Export Data Projects in your D365FO environments<\/span><\/p>\n

\n

Create an Export Data Project on the basis of the Data Template from SharePoint and pick “XML Element” and “Data Package” for the output format. As per best practice, suffix the Data Project with the name of the environment for easy identification later. Note that in case you have many D365 FO environments to continuously apply updated Data Templates to, you could consider Data Task Automation.<\/a>
\n\"D365FO<\/a><\/p>\n

\n

STEP 3<\/strong>: Save the files in a central location<\/span><\/p>\n

\n

Create a folder structure in a central location. If you use SharePoint as a baseline, then open the respective Document Library in OneDrive to allow sync to local folders. Then, run the Export Data Projects in the various D365FO environments, download the packages and extract them into the folder structure:<\/p>\n

\"Setup<\/a><\/p>\n

\n

STEP 4<\/strong>: Install and configure Altova diffdog<\/span><\/p>\n

\n

To quickly compare Configuration from D365FO environments by the XML files we’ve exported, I prefer using a tool called Altova diffdog<\/a>. Although the tool is not free (one-time EUR109\/USD139 for a license), I think it’s worth the investment looking at the excellent way this tool highlights any differences at a glance – We’ll come to that below. First, download and install the tool (on a trial license) and configure as follows:<\/p>\n