This article describes how to install the Ariene source code models into a Dynamics 365 Finance & Operations development environment. This process is intended for organizations or partners who want full access to Ariene’s source code in order to customize, extend, or deeply integrate the solution.

The installation consists of importing two AX model files (ATLODEX and ATLOELS) and then checking the correct artifacts into source control while excluding generated and non-source assets.

Prerequisites

Before proceeding, make sure you have:

• A Tier-1 (DEV) D365 F&O environment
• Local access to the PackagesLocalDirectory (generally K:\AosService\PackagesLocalDirectory in a cloud hosted environment or C:\AosService\PackagesLocalDirectory in a local VM)
• ModelUtil.exe available (under the bin directory, K:\AosService\PackagesLocalDirectory\bin or C:\AosService\PackagesLocalDirectory\bin)
• Credentials to download Ariene source files
• A configured source control repository (Azure DevOps / TFVC or Git)

Step 1 – Download the Ariene Model Files

The Ariene source models must be downloaded from the Atlantic Oak website:

https://atlantic-oak.com/Downloads/ArieneDownloads

At the bottom of the page, locate the section titled:

Ariene Model Files

This section provides access to the ZIP file containing the Ariene source models. Access requires valid credentials. Download the ZIP file ARIENE_MODEL_FILES_V002.000.004.000.zip and extract it locally under the root of the C:\ drive. Under C:\ARIENE_MODEL_FILES_V002.000.004.000\ you should see files similar to:

ATLODEX.axmodel
ATLOELS.axmodel

Step 2 – Remove Existing Models (If Previously Installed)

If Ariene was previously installed and checked into source control, the safest approach is to completely remove the existing models before importing the new ones.

Navigate to:

 K:\AosService\PackagesLocalDirectory 

Delete the following folders:

ATLODEX
ATLOELS

After deleting these folders, check in the deletions to source control. This ensures a clean baseline before importing the updated models.

Step 3 – Import the Ariene Models

Open a command prompt as Administrator and run the following commands:

K:
 cd "K:\AosService\PackagesLocalDirectory\bin"
 ModelUtil.exe -import -metadatastorepath="K:\AosService\PackagesLocalDirectory" -file="C:\ARIENE_MODEL_FILES_V002.000.004.000\ATLODEX.axmodel"
 ModelUtil.exe -import -metadatastorepath="K:\AosService\PackagesLocalDirectory" -file="C:\ARIENE_MODEL_FILES_V002.000.004.000\ATLOELS.axmodel" 

Adjust the file path as needed to match the location where you extracted the ZIP file.

Once the commands complete successfully, the models will appear under PackagesLocalDirectory.

Step 4 – Check the Correct Artifacts into Source Control

After importing the models, you must check the source code into source control. It is critical to include only the correct folders and files.

ATLODEX Model

For ATLODEX, check in only the following folders:

• ATLODEX
• bin
• Descriptor

The following folders must be excluded:

• Resources
• XppMetadata

Additionally, exclude the following generated files:

BuildModelResult.log
BuildModelResult.xml
CompileLabels.xml

Inside the ATLODEX bin folder, check in only these DLLs:

AODXCrypto.dll
AODXFTP.dll
AODXSFTP.dll

No other binaries should be checked in.

ATLOELS Model

For ATLOELS, check in only:

• ATLOELS
• Descriptor

Do not check in a bin folder for ATLOELS. No Resources, XppMetadata, or generated build files should be included.

Step 5 – Final Notes

After the correct artifacts are checked in, the Ariene source models are fully installed and under source control. The solution can now be customized, extended, and built using standard D365 F&O development practices.

Always ensure that generated artifacts are excluded from source control to avoid build inconsistencies and unnecessary merge conflicts.

For support or questions regarding Ariene source models, contact Atlantic Oak.