Tag Archives: model

Check Installed Models Script

I’m working in an environment with 3 different AOSs. I have to maintain many models and hotfixes. Therefore, I need to find a clever way to determine whether or not a specific hotfix was installed on an environment


Use the attached script,  and then execute it in AX Management Shell and follow the prompts.


$found = $false
$server = read-host "Enter the database server that hosts your modelstore database (Default is localhost)"
if ($server -eq ''){ $server='localhost'}

$db = read-host "Enter the name of your AX model store database (Default is MicrosoftDynamicsAx)"
if ($db -eq ''){$db = 'MicrosoftDynamicsAx'}

$kb = read-host "Which KB are you attempting to install?"

while ($kb -eq '')
   $kb = read-host "You must enter a Kb to search for, try again (enter a KB now)" 

$models = Get-AxModel -server $server -database $db

foreach ($model in $models)
    $manifest = Get-AXModelManifest -Server $server -Database $db -model $model.Name 
    $details = $manifest.Details
    if (Select-String -Pattern $kb -InputObject $details)
        $found = $true

if (!$found)
    "KB " + $kb + " was not found in any installed model"
Leave a comment

Posted by on February 11, 2014 in Installation and Configuration


Tags: , , , , ,

How to upgrade a new model file form an ISV with conflict

Step 1: Install a model

  1. axutil.exe delete /model:YOUR_EXITING_MODEL_ID /config:”YOUR_AOS”
  2. axutil.exe import /config:”YOUR_AOS” /file:”C:\YOUR_PATH\YOUR_MODEL_FILE.axmodel” /conflict:push /verbose

Step 2: Find Conflict  model

The process will create a conflict model if found image


Step 3: Create a project from a conflict model

  1. Open the Development Workspace.
  2. Choose Tools > Model management > Create project from model.
  3. Select the model that will be used as the source of the project content.
  4. Supply the name of the new project to be created.
  5. Click OK. The project will be created that has the elements from the model.

A project will provide project name will be created in private project

Step 4: Resolve conflicts

Go to your project and start selecting a resource that has conflict.

Compare to see the differences between the resource in the patch layer and the resource in the main layer.

There are many ways to resolve the conflict, depending on the resource type and the actual conflict. Some of the ways to resolve the conflict include the following:

  • Use the information and the available actions from the Comparison window to merge changes from the conflict model into an existing layer.
  • Make a change in the resource in an existing model in the current layer. For example, if two different models in the layer have modified the same resource, you could consider creating a new “shared” model in the layer that contains a single version of the resource that can be used by both of the other models.
  • Switch to the patch layer and modify the resource there. In some cases, this is the easiest way to resolve the conflict.

Repeat this process until there isn’t any object to resolve.

1 Comment

Posted by on January 15, 2014 in Installation and Configuration


Tags: , , , ,

%d bloggers like this: