In complex reverse proxy situations, relying on the "server": address or the "usePublicURLFromServer" / "Public Web Client URL" being the correct URL for debugging is not always a correct assumption.

Sometimes these URLs are dynamic and per-session and can't be set on the service tier. Or, the Server address mismatches because of different ports (developer services vs. web client).

Instead, I propose that "launchUrl" should just be a parameter that can be manually set so there's no doubt about which to use in a particular debugging configuration.

  • The debugging context and information would be appended and opened in the browser.
  • Default would be empty, which then falls back to respect the settings of "server" and "usePublicURLFromServer"

This doesn't impact any existing configurations and can be added manually as an advanced option.

This is similar to other debugging behaviours in VS Code, i.e. a c# program lets you define the full launch parameters when debugging instead of "forcing" values on you.

Category: Development
Needs Votes
Ideas Administrator

Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team