Fixed Issues and Known Issues
| Issue # | Description |
| IH-17325 | BuildAndDeploy.ps1 no longer hangs indefinitely during baseline download on machines where Azure CLI has not been previously configured. The script now automatically applies the required Azure CLI configuration before downloading the baseline, allowing the process to complete without manual intervention. |
| IH-17500 | Deploy pipelines to UAT, STG, and Production now complete successfully for single-region environments. Previously, deployments could fail unexpectedly if no additional regions were configured. |
| IH-10974 | For SDEs referencing the When updating to Aras DevOps 1.15, please manually migrate existing |
| IH-16536 | Aras DevOps now supports deploying Aras Innovator instances with Edge Eventing and AI Search enabled via standard pipelines, automatically including newly entitled components in all deployments, delivering new versions without manual repository changes. |
| IH-11729 | CI/CD pipelines now copy a pre-loaded baseline database directly from Azure SQL Elastic Pool instead of restoring from a .bacpac file on every run, significantly reducing build time by preserving the restored database for future use. |
| IH-11380 | SDEs now store only customer-specific AML changes instead of both released Aras Innovator AML packages and customizations, reducing repository size, eliminating unnecessary merge conflicts, and ensuring Git diffs reflect only customizations. |
| IH-11568 | When CIAM integration is enabled for the SDE, Aras DevOps now automatically creates a corresponding CIAM application at deploy time and removes it when the Innovator instance is removed eliminating manual CIAM setup. |
| IH-17771 | New-ArasDevOpsRepository now automatically enables the AutoResolveItemDependency feature for all newly created SDEs by setting the Import.AutoResolveItemDependency property to true in default.settings.include, eliminating additional manual configuration for new customers while preserving existing settings for current customers. |
| IH-17666 | To customize environment prerequisites requirements for LDE, add SetupEnvironment.config.json to AutomatedProcedures folder of your repository. Aras DevOps will use it instead of the module default values so no changes to the Aras DevOps module required. |
| IH-11717 | All Aras DevOps LDE scripts and PowerShell module commands now support the -help option, enabling inline discovery of available parameters and options without consulting documentation, reducing setup friction in the LDE. |
| Issue # | Description | Workaround |
| I-050998 | When a user executes The Get-ArasDevopsPackagesList of the Powershell module, only the latest versions are displayed for IOM and InnovatorConfigs. It should display this package’s latest version of the current Innovator version. | The commandlet was originally created due to nuget.exe failure to display upstream package versions when listing. Standard Find-Package is capable of properly listing packages and this commandlet is not needed anymore. Get-ArasDevopsPackagesList command is therefore obsolete and will be deprecated. |
| I-058395 | In the Local Development Environment, the BuildAndDeploy.ps1 fails on the install step of Visual Studio 2022 Build Tools when there is a pre-existing installation of Visual Studio Build Tools. |
|
| I-058883 | In the Local Development Environment, ContinuousIntegration.ps1 fails if using Aras Innovator Container Deployment in Aras Enterprise and displays the following error: <The sp_configure value “contained database authentication” must be set to 1 in order to restore a contained database. You may need to “RECONFIGURE” to set the value_in_use. RESTORE DATABASE is terminating abnormally> | In the SQL Server on the local machine, enable the contained database authentication option. The option can be enabled by two ways:
|
| I-059096 | When deploying on a local machine, users may see an error message directly from SQL Server that the password validation failed. The error message may look like:"System.Data.SqlClient.SqlException: Password validation failed. The password does not meet the operating system policy requirements because it’s too short” | Deployment of Aras Innovator on a user’s machine relies on local SQL Server that defines policies for SQL user passwords. Aras uses 2 SQL users named “innovator” and “innovator_regular”. Passwords used during deployment are defined in Machine.Settings.include Make sure that both users can log into SQL Server using defined password before launching new deployment. |
| I-059899 | When an existing project moves to a container-based deployment, it is possible that the initial repository contains some modified configuration files. In this case, the deployment will not be successful. | A customer repository should not contain any configuration files. The modifications to configuration files that might be required in the context of a project needs be described using Config Transformations feature available with the service. |
| I-072044 | Chocolatey Version Update In Aras DevOps 1.10, an updated version of Chocolatey is now used to meet enhanced security requirements. Since two versions of Chocolatey cannot run simultaneously on the same machine, users must manually downgrade Chocolatey if they need to work on projects that reference an older version of Aras DevOps. | Manually downgrade the version of Chocolatey. |
| I-073506 | The Generate Baseline pipeline may intermittently fail when used with unpatched Aras Innovator versions lower than Release 32. | Retry the Generate Baseline pipeline execution. |
| IH-10423 | After upgrading to Aras DevOps 1.13, the Selenium Tests pipeline may fail (pipeline status turns yellow) when used on Software Development Environments (SDEs) running Aras Innovator 14.0.6 or earlier. This occurs because updated test logic in BDS 1.13 is no longer compatible with end-of-life Aras Innovator versions. Upgrade Aras Innovator to a supported version to restore compatibility. |