Finance | Project Operations, Human Resources, ...

Knowing Code repository a D365 instance pointing to

(0) Share

Report

Posted on by CU21071332-0

Hi,

I wonder if there anyway (out of the box OR using customization) to know where a D365 instance pointing to.

We have few env and each one has different code bases.. from looking at URL its not always obvious that which Repo branch its using.

for example a Env with URL https://lcs-TEST1194f6be3259ec80daaos.axcloud.dynamics.com/ , there is no way to tell where its pointing to unless someone has access to remote machine.

If not available OOTB , we may consider adding some form or workspace with all these linkage info.

All responses (3)

Answers (0)

Sort by

Suggested answer

André Arnaud de Cal... 307,808 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi,

When creating development environments, you can provide your own naming. You can consider including the branch as part of the VM name. At my company, we also have a lot of environments as we are a global ISV. We have naming conventions to indicate the product, branch and user or purpose. E.g. we have DQS-DEV-AAC to indicate it is a VM for Data Quality Studio, branch Development and it is my sandbox.
Suggested answer

Kevin Xia Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi，

Depending on the problem you describe, it seems that you are interested in distinguishing which environment or code inventory the instance is in the problem. You can add the corresponding parameters to the URL to indicate the current environment or code base, such as URL https://lcs-TEST1194f6be3259ec80daaos.axcloud.dev.dynamics.com/ or https://lcs-TEST1194f6be3259ec80daaos.axcloud.dynamics.com?env=dev.

Of course, Custom Metadata is also a solution. Develop a custom solution that integrates with your version control system (e.g., Git, TFS) and retrieves the branch or code repository information based on the environment. This solution can then display the relevant details within Dynamics 365 or any other preferred interface.

Best regards,

Kevin
Martin Dráb 241,467 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Note that non-development environments aren't connected to source control,. They also don't have any information about where their code came from, because they've got a deployable package and they don't know where the original source code is stored. If you don't have any naming convention (as others suggested) nor you store this mapping anywhere, you'll need to extract this information from Azure DevOps. Release pipelines tells you what was deployed to which environment, and build pipelines tell you what code was used for it.