Get in touch

AX Client - Import XPO

Imports an XPO into an AX 2009/2012 environment

TopicWork with AX client (AX 2009/2012)
CategoryBuild
Special features
  • Run options:
    • Classic (uses -AOTIMPORT=)
    • Direct (uses Autorun file)
    • Batch (add to existing Autorun file and execute later)
  • Set layer name (optional)
  • Set layer code (optional)
  • Set model name (optional)
  • Set delete subelements (optional)
  • Set import with ids (optional)
  • Set suppress compile errors (optional)
  • Set suppress import elements (optional)
  • Set max wait time (optional)
Microsoft documentationhttps://technet.microsoft.com/en-us/library/aa854197.aspx

Parameters

ParameterTypeRequiredDefaultExample
XPO file path (.xpo)The file path of the xpo file.File pathTrue—$/Microsoft Dynamics AX (Test)/MyCombinedFile.xpo
Run modeHow should the step be executed? Possible values are "Direct", "Classic" or "Batch". The option "Direct" will create and use an autorun file to execute the build step. The option "Classic" will use "StartupCmd" and the option "Batch" adds the build step to an existing autorun file. To execute the existing autorun file use the Build step "AX Client - Execute autorun xml file". To create an empty autorun file use the Build step "AX Client - Create empty autorun xml file".File pathTrueDirect—
Client config file path (.axc)The file path of the client configuration file.Depends on: Only visible if Run mode is not "Batch"File pathTrue——
Layer nameSpecifies which layer to open in the AOT.Depends on: Only visible if Run mode is not "Batch"StringFalse—VAR
Layer codeSpecifies the developer license code for developer options.Depends on: Only visible if Run mode is not "Batch"StringTrue—SDSA43432DSADSADAS
Model nameThe "current model" is the model where all new AOT elements are created in.Depends on: Only visible if Run mode is not "Batch"StringFalse—MyModel
Delete subelementsShould the subelements deleted?Depends on: Only visible if Run mode is not "Classic"BooleanFalseTrue—
Import with idsShould the ids imported?Depends on: Only visible if Run mode is not "Classic"BooleanFalseFalse—
Suppress compile errorsShould the compile errors suppressed?Depends on: Only visible if Run mode is not "Classic"BooleanFalseFalse—
Suppress import elementsShould the import elements info suppressed?Depends on: Only visible if Run mode is not "Classic"BooleanFalseFalse—
Log file path (*.log)The file path to save the log file to.Depends on: Only visible if Run mode is "Direct"File pathTrue—$/Microsoft Dynamics AX (Test)/MyAutorunLogFile.log
No compile on importShould the imported xpo compiled?Depends on: Only visible if Run mode is "Classic"BooleanFalseFalse—
Max wait time (min)The number of minutes to wait before failing the step.Depends on: Only visible if Run mode is not "Batch"IntegerFalse120—
AutoRun file path (*.xml)The autorun file to append the build step to.Depends on: Only visible if Run mode is "Batch"File pathTrue—$/Microsoft Dynamics AX (Test)/MyAutorunFile.xml