| Topic | Work with Models (AX 2012) |
|---|---|
| Category | Package |
| Special features |
|
| Microsoft documentation | https://technet.microsoft.com/en-us/library/jj720288.aspx |
Parameters
- Server config file path (.axc)
- Model file path (.axmodel)
- Conflict mode
- Targer layer name
- Replace model name
- Do not optimize
- Create parents
- Show model details
| Parameter | Type | Required | Default | Example |
|---|---|---|---|---|
| Server config file path (.axc)The file path of the server configuration file. | File path | True | — | $/Microsoft Dynamics AX (Test)/Server.axc |
| Model file path (.axmodel)The file path of the ax model file. | File path | True | — | $/Microsoft Dynamics AX (Test)/MyModel.axmodel |
| Conflict modeSpecifies what to do in the event that a conflict of element IDs between the model being imported and another model in the same layer is found. Possible values are "Reject", "Push", or "Overwrite". Reject stops the import process. Push duplicates the model element into the related update layer. For example, for the ISV layer, the update layer is ISP. Overwrite replaces the existing model element with the imported model element. | Picklist | True | Reject | — |
| Targer layer nameSpecifies which layer a conflict model should be created in. It must be a layer above the layer that the model itself is imported into. The default value is the patch layer of the layer that the model itself is imported into, or, if importing into a patch layer, to the USR layer.Depends on: Only visible if Conflict mode is "Push". | String | False | — | VAR |
| Replace model nameSpecifies a model to be replaced by the model that is being installed. | String | False | — | MyModel |
| Do not optimizeSpecifies that the system skip steps to optimize the database, such as re-indexing. After installation is finished, you would then call the Build step "AX 2012 Model Store - Optimize". | Boolean | False | False | — |
| Create parentsSpecifies that if you install a child element that does not have a parent in the model store , a new parent element should be created. By default, this option is off, so that if child elements that do not have parents are encountered, the import process is stopped. In general, we recommend that you avoid the use of this parameter, if possible. If you are importing multiple models that have dependencies, we strongly recommend that you import them in the correct order, so that the use of the Create Parents parameter is not required. If you must use Create Parents, then we recommend that you use it in combination with the Conflict mode set to Push, and then resolve issues with the parent elements in AOT. Note that if you use the Create Parents parameter, a new model of Category virtual will be created. | Boolean | False | False | — |
| Show model detailsShould the model details be shown? | Boolean | False | False | — |