Export (0) Print
Expand All

Combine XPO Tool User Guide [AX 2012]

Updated: December 16, 2013

Applies To: Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

The Microsoft Dynamics AX 2012 Combine XPO Tool is a command line program that combines a set of interdependent XPO files into a single XPO. For example, if a team of developers is making code changes to different aspects of an application, they can use this tool to merge those changed files into one XPO file.

As of AX 2012 R2, the Combine XPO Tool is available in the Microsoft Dynamics AX\60\Management Utilities folder. (The beta version of the tool was previously available on InformationSource).

The Combine XPO tool generates an XPO file that is a combination of the XPO files in a given folder and any subfolders. It takes the path to the folder and the name of the resulting XPO file as input. For example, if you have XPO files in the C:\MyApplication\ModelA folder, you would use the following commands to create the combined XPO file:

CombineXPOs.exe -XpoDir c:\MyApplication\ModelA -CombinedXpoFile c:\MyApplication\AXModelAFiles.xpo

The parameter –XpoDir is the location of the folder that contains the xpos you want combined and imported. The –CombinedXpoFile parameter is the resulting directory path and filename of the newly created combination XPO file. Once the combined XPO file is successfully created, you import it into Microsoft Dynamics AX in the same manner as individual XPOs. For more information on importing XPOs, see How to: Import Application Objects by Using the AOT.

The following table lists the available command line parameters for CombineXPOs.exe, how they are used and if they are required. For parameters without a value listed in the argument field, no value is necessary.

Parameter

Argument

Optional?

Description

-XpoDir

<directory>

No

The root directory of the XPO source code.

-CombinedXpoFile

<path and file name>

No

The path and filename for the resulting combined XPO file.

-SpecifiedXpoFile

<filename>

Yes

A file containing a list of XPO files to include in the combined file. The files specified must reside under the –XpoDir path. Any XPO files not in this list will not be in the combined file. The list should be formatted to show the full path to each file with one value per line. For example:

C:\ProgramData\myfile1.xpo

C:\ProgramData\myfile2.xpo.

All XPO files in the folder identified by the –XpoDir parameter are included in the combined file if this parameter is not passed.

-NoDel

<filename>

Yes

A file containing a list of XPO files that contain DEL_ fields and indexes to include in the combined file. Any XPO files not in this list will have their DEL_ fields and indexes removed prior to being imported into the combined XPO file. The list should be formatted to show the full path to each file with one value per line. For example:

C:\ProgramData\myfile1.xpo

C:\ProgramData\myfile2.xpo.

-Verbose

Yes

Enables verbose mode, which displays the name of each XPO file as it is processed

-utf8

Yes

Produce a UTF-8 output file.

-Threads

<count>

Yes

Use this to reduce the load on the CPU if the process is negatively affecting other applications. The default is to let the Microsoft .NET Common Language Runtime automatically determine this count.

-ExclusionsFile

<filename>

Yes

The file specified includes a list of XPO files that should be excluded from the combined file. Any XPO files in this list will not be in the combined file. The list should include the full path to the file to be excluded with one file on each line. For example:

C:\ProgramData\myfile1.xpo

C:\ProgramData\myfile2.xpo.

-ViewsOnlyOnce

Yes

Causes any view XPOs to be included only one time each in the combined output. Otherwise, multiple copies of the view XPOs will be included because this typically improves reference resolution for queries and views during import. Using this parameter may improve the performance of loading the combined XPO file, but may also lead to reference errors when loading the XPO.


Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

Show:
© 2014 Microsoft