Debug X++ against copies of production databases
This topic explains how to configure X++ debugging so that you can investigate issues in the production environment. For this procedure, you make a copy of the production database and then configure a developer environment to connect to the copy.
When an issue that requires X++ debugging occurs in a production environment, the system administrator and developer work together to configure debugging and then debug the issue. The following illustration shows an overview of the process.
- In Microsoft Dynamics Lifecycle Services (LCS), the system administrator requests that a copy of the database be connected to the sandbox user acceptance testing (UAT) environment. (In other words, request a database refresh.)
- In Microsoft Azure DevOps, the developer synchronizes the local code to the same build that is running in the production environment.
- In the sandbox instance of Microsoft Azure SQL Database, the system administrator creates a temporary SQL sign-in for the developer. The developer then configures the environment to connect to the sandbox database.
- A firewall exception is added so that the developer environment can connect to the sandbox database.
- The developer debugs the issue.
When debugging is completed, the system administrator can remove the temporary sign-in from the sandbox SQL database.
Before you begin
Before you begin to configure X++ debugging in a production environment, note the following points:
You can't debug directly against the production environment, because debugging might cause data corruption. However, developers can manipulate values at runtime. Alternatively, in their own instance, developers can make a code change that changes data.
The developer environment that is used for debugging must exist in the same LCS project as the sandbox environment, and both of them must be Microsoft managed. This requirement helps strengthen the security of the sandbox database. By default, there is a firewall restriction on both the sandbox and production SQL databases. This restriction allows only servers in those environments to connect to the databases. To enable debugging, a firewall exception is added so that a developer environment can connect to the sandbox database.
A one-time manual change to the developer environment is required, so that the IP address of the environment can connect to the sandbox database. Create a support request with Microsoft support asking to allow the IP address.
We recommend that you not use a build environment for debugging. Otherwise, there is a risk that the developer's activities on the computer might break the automated build process.
When an issue occurs in the production environment, the system administrator can sign in to LCS and request that a database copy be added to a sandbox environment. While the database copy is running, the system administrator can notify the developer of the issue. The developer can then synchronize to the correct build of the code to match the production environment.
In Microsoft Visual Studio, in Source Control Explorer, right-click the root node of the branch to synchronize, and then select Advanced > Get specific version.
In the dialog box, select Type=Label, and then select the ellipsis (...).
In the dialog box, select Find. All the builds from the build server are listed.
Select the build that is currently deployed in the production environment, and then select to run a full build. When the database is copied, only the system administrator will be able to access the sandbox database. The system administrator must complete the following tasks:
Remove any data that you don't want in the sandbox database, such as employee salaries.
Enable or add the developer as a user.
Create a new SQL sign-in that the developer can use. This step lets the system administrator maintain the security of the sandbox environment. The developer will have access to one database for only a limited time. Use the following code to create the new SQL sign-in.
CREATE USER devtempuser WITH PASSWORD = '' EXEC sp_addrolemember 'db_owner', 'devtempuser'
Next, the developer edits the web.config file for Application Object Server (AOS).
Go to J:\AosService\WebRoot\web.config.
Save a copy of the original web.config file, so that you can switch back later.
Edit the following section in the web.config file.
Before your changes
<add key="DataAccess.Database" value="sandboxDatabaseName" /> <add key="DataAccess.DbServer" value="sandboxDbServerName.database.windows.net" /> <add key="DataAccess.SqlPwd" value="password" /> <add key="DataAccess.SqlUser" value="devtempuser" />
After your changes
<add key="DataAccess.Database" value="TariqRTW_axdb_dd78f8aadbc6c481" /> <add key="DataAccess.DbServer" value="vyxx2dflyo.database.windows.net" /> <add key="DataAccess.SqlPwd" value="P@ssw0rd" /> <add key="DataAccess.SqlUser" value="devtempuser" />
Debug the issue.
After the developer has finished, the system administrator can remove devtempuser from the sandbox database. This step prevents the developer from having permanent access to the sandbox database.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.