15. Note: If the local version of the file is already up to date, “get latest” does not load the file into Microsoft Dynamics AX. Microsoft Dynamics AX and the local TFS repository should always be in sync. If you have synchronized the XPO file from outside the Microsoft Dynamics AX environment (by using Team Explorer or another tool), you must manually load the XPO into Microsoft Dynamics AX.

20. AX elements (Metadata) are associated with corresponding business data based on their element ID. Element IDs are specific to each installation and are sometimes referred to as installation-specific IDs. When two AX environments share copies of the same business data (Such as transaction, configuration or master data), these environments need to also share the same element IDs

22. XPO filesModel filesModel store files Installation tool AX development workspace (MorphX) AXUtil.exe or Windows PowerShell cmdlets The files can be signed? NoYesNo Element IDs are preserved on target model store? All elements that already exist in the model store preserve their IDs (XPO files don’t contain IDs). For new elements, new IDs are generated. All elements that already exist in the model store preserve their IDs. For new elements, new IDs are generated. All element IDs on target system become equal to IDs store in the model store file. Compilation is required after installation? Yes No CIL generation is required after installation? Yes No

25. Do Not Delete Models on the Staging System! Same procedure used for deploying models on a test environments One important exception: Skip the step where you delete the current version of your models in order to maintain common element IDs with the production system.