DMT - data migration tool (not dimetiltriptammina)
Few points to take into account planning the use of this tool:
1) should I install the ApplicationHotfix or the CombinedXPO?
2) where can I get support or confront with?
3) is there a bug in the way passwords are managed in the latest kernel and rollup of Ax2009?
Application hotfix or CombinedXPO
Once you get the latest version of the feature from the dedicated Yammer Group (Ax2009 Migration - Files), you are in front of the dilemma about what to do with the combinedXPO. Is it preferrable to install the application hotfix or patch the code manually merging the differences with the XPO? The official documentation states that they are equivalent, but they are actually NOT. The approach that I may suggest is to consider both of them, but carefully.
Indeed, it seems that most of the functionalities have been implemented better in the application hotfix, but you need few from the xpo as well. Which ones? First of all you should merge the fixes mentioned in the Release Notes, on DMTCustomerAddressView and DMTVendorAddressView; and take into account the logics managing the Service Application ID, user name and password to connect to the cloud instance. In short, take care of the new DMTParameters. On the contrary, do NOT import the DMT configuration key, unless you want to definitely compromise the installation of the object server instance, which you won't be able to restart anymore unless deleting the layer where you get it imported.
Recommended by LinkedIn
Get support in yammer group
Most of the issues you are likely to encounter have already been discussed and addressed in the Ax2009 migration group, which you can get access to via the Dynamics ax feedback program. The issue about the length associated with the DMTName is common and the solution consists in augmenting its length; otherwise it's not possible to generate the initial maps. If you cannot find any scenario fitting yours in the group, post your question putting in cc someone in Microsoft such as Bhaskar.r , in order to maximize the chances to receive a valuable answer.
Validate Target Service issue
On RollUP 8 of the Application and Kernel Version 5.0.1600.4461 there is an issue on the decryption of the password associated with Dynamics365PasswordStr. Any time it gets decrypted, it is truncated losing its final character, independently of its length. A possible temporary workaround to get the target service validated proceeding with the generation of the maps may consist in changing dynamically its value in debug mode.