web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Cannot choose the Production DP in the Visual Studio in the Production site.

(0) ShareShare
ReportReport
Posted on by

Problem : Cannot choose the AX2012 Production DP in the Visual Studio in the AX2012 Production site.

The visual studio is in the AX2012 Production site, but I cannot choose the AX2012 production DP in this visual studio. Would all the experts tell me how can I solve this problem, please? is this issue about the visual studio setting? Please give me the advise. Thank you.

*This post is locked for comments

I have the same question (0)
  • Martin Dráb Profile Picture
    239,381 Most Valuable Professional on at

    What do you mean by "Production site"? That you're developing customizations directly in a production environment? If so, immediately abandon this crazy idea! Develop changes in a development environment (and store them in a version control system), then let testers to verify the functionality in a test environment. Only when the version of application is approved, deploy it to production.

  • Community Member Profile Picture
    on at

    I have three sites in my company. They are Dev, Prod and Live. When I choose the Prod DP in the Visual Studio which connect to Prod site, the DP are not Prod DP. All the DP(s) which can let me choose are in DEV DP. That I don't know how to fix it.

  • Martin Dráb Profile Picture
    239,381 Most Valuable Professional on at

    You're soo lucky! You almost started to meddle with then production application, which could potentially disrupt the whole production environment! You mustn't ever do it! DON'T DEVELOP IN PRODUCTION!!!

    Please isolate your production environment so that developers can't connect to it directly, therefore they can't destroy the production application by mistake or ignorance.

    You're fixing a completely wrong problem.

  • Suggested answer
    Vilmos Kintera Profile Picture
    46,149 on at

    I agree with Martin on doing changes in Production is hazardous.

    If I review an implementation and find practices like that, it usually means a lot of negative points for the partner or team.

    The solution to your problem that why doesn't Visual Studio connect to the correct environment is because VS is using your registry settings for identifying to which environment to connect to. Those settings can be modified using the AX Client Configuration utility in the Control panel > Administrative tools menu within Windows. You need to point both the Local client and the Business Connector settings from the dropdown to the correct environment, then start Visual Studio using elevated rights. Please make sure your client configuration never points to Production instance directly for development purposes!

  • Vilmos Kintera Profile Picture
    46,149 on at

    Can you please make sure you tick the checkboxes for helpful answers next to each post, so the topic gets resolved? Thank you.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 39

#2
Michel ROY Profile Picture

Michel ROY 14

#3
imran ul haq Profile Picture

imran ul haq 8

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans