When recording a Page Script in Business Central Online and using the "Share" functionality to copy the link, the generated URL does not include the environment name where the recording was made.

Current behavior: The shared URL always points to the Production environment, following this pattern: businesscentral.dynamics.com/[tenant-guid]/do?company=...

This happens regardless of which environment (Sandbox, custom named environment, etc.) the recording was originally created in.

Expected behavior: The shared URL should include the environment name in the path: businesscentral.dynamics.com/[tenant-guid]/[environment-name]/do?company=...

Impact: This limitation creates several workflow issues:

1. Testing in sandboxes: When creating test scripts in sandbox environments, shared links redirect colleagues to Production, forcing manual URL modification before testing
2. Documentation: Links saved in documentation or wiki pages become environment-agnostic, requiring extra instructions on how to modify them
3. Cross-environment collaboration: Teams working across multiple environments (DEV, TEST, PROD) cannot reliably share recording links without manual intervention
4. Risk of errors: Users might accidentally execute test scripts in Production when they intended to run them in Sandbox

Proposed solution: Capture the current environment context when generating the shareable link, and automatically include the environment name in the URL structure. This would make the Page Scripting share functionality truly environment-aware.

Business value:

• Reduces friction in UAT workflows across sandbox and production environments
• Minimizes risk of accidentally running test scripts in wrong environments
• Improves collaboration between consultants, developers, and end-users
• Aligns with best practices of environment-specific testing

This enhancement would significantly improve the usability of the Page Scripting tool for organizations using multiple Business Central environments.