Why Am I Getting This “No Repository Folder Has Been Specified” Message in Dynamics AX?
This blog post talks about a recent Help Desk case we resolved for a customer that had to deal with the version control parameters, and how version control is managed in different versions of Dynamics AX or Dynamics 365.
A manufacturing customer reported an issue that their users were getting an Infolog pop-up message when they opened a new session, and the message stated “No repository folder has been specified”. Whether by mistake or unintentional, a user had changed the version control parameters form. This parameter change caused the issue for all other users who opened a new session thereafter. This did not remove or delete any data in the system. It was just an error message informing the user(s) that something was missing in a setup somewhere. Users could close the Infolog and go about their daily life inside the system.
To resolve the issue please change the version control parameters in Dynamics AX. For our customer’s specific situation the Source control status field was set at Enable so we changed it to Disable and everything went back to normal – no more annoying message pop-up.
If you are not a developer and have never worked with or setup a version control system, then you probably don’t know what a repository folder is. It is not something that is common-knowledge among everyday users.
What is a version control system?
This is sometimes referred to as Source Control. This kind of software helps developers and development teams track their code changes over time, and to recall a specific version later on if needed. One of the most common version control systems is Git. To learn more about Git, click here.
What is a repository folder?
This is a folder, in the local file system, on the administrator or developer’s computer that is used to receive a local copy to edit when items are checked out.
In Dynamics AX 2009, managing the version control parameters can be done by using the “Microsoft Dynamics AX” drop-down menu located in the upper-left corner. This is also known as the “File” menu in Dynamics AX 2012.
Click Tools > Development tools > Version control > Setup > Parameters.
To learn more about Version Control System, click here.
In Dynamics AX 2012, managing the version control parameters is done by using the development workspace. It is not accessible using the File menu, like you would in AX 2009. Accessing the development workspace takes a special security role like System Admin or Developer access. Everyday users who are assigned roles like ‘Warehouse Clerk’ or ‘Supervisor’ would not have access to this and for good reason. Only those who need access to the development workspace should have it.
With the development workspace opened, click Version Control > Version Control Parameters.
For more information about Setup Local Version Control Parameters, click here.
In Dynamics 365, managing version control is done through Azure DevOps (formerly known as Visual Studio Online). Azure DevOps is a Software as a service (SaaS) platform from Microsoft that provides an end-to-end DevOps toolchain for developing and deploying software. Version control, aka Source Control, is a part of Azure Repos.
As noted below in the screenshot, there are six major pillars to Azure DevOps. How these pillars work together is described in a workflow further down.
The workflow shown above describes how a requirement from a Customer flows from the Azure Boards, to the Repos, through the Pipelines, into Deployment Environments, to the Test Plans, through the Business Users, and finally deployed to the Production environment.
To learn more about configuring Azure DevOps for Dynamics 365, click here.