Metadata Compare can be found under org-level settings and utilities, and can be accessed from the gear icon in the Axsy Config Tool.
Metadata Compare
This tool is a significant aid for support and troubleshooting as it allows you to quickly compare all of the metadata between config versions.
Many support problems are due to a change taking place in your Salesforce org setup and / or with your Axsy Config. This tool lets you quickly identify any changes between config versions to any of metadata used by the Axsy Mobile app. As this metadata includes changes made outside of the Axsy Config Tool, for example to Flows and Page Layouts, you can quickly locate changes and determine the impact on the Axsy Mobile app functionality.
This tool also allows you to inspect changes for information purposes, for example, if you wanted to track the evolution of your config versions over time.
Draft Configs
You can also use this tool to compare Draft configs to previously published versions by generating the necessary metadata for comparison purposes, as shown in Figure 1.
Figure 1 - Generate Metadata Option For Draft Configs
Once the metadata has been generated, it is possible to compare metadata between config versions as shown in the example below. If necessary, the metadata can also be updated as shown in Figure 2.
Figure 2 - Update Metadata Option For Draft Configs
Example
In Figure 3, we show a comparison between the two most recent config versions. The list shown is scrollable, and we can see that the Account object has changed.
Figure 3 - Comparison Of Config Versions
When clicking on "Modified" in Figure 3, the two metadata files are shown for this specific comparison as shown in Figure 4. This can be further refined by enabling "Only show differences" as shown in Figure 5.
Figure 4 - Comparing Account Metadata Between Config Versions
Figure 5 - Comparison With Only Show Differences Enabled
When comparing the metadata between two config versions, all additions are highlighted in green. Any metadata that has been removed is highlighted in red. In the above example, we can determine that a new custom field was added in Version 0053.