[Bug]: database name field changes after selecting package file in deploy #20458
Description
Description
I launched the dialog from a specific database, then selected a package file (it defaulted to deploy)
the database name field immediately changed to match the dacpac name instead of forcing it to stay on the existing DB I had selected as the context.
The expected behavior would be for the database name field to stay the same and remain unaffected. Having it change, when the user does not expect it could cause issues.
Steps to Reproduce
- Right click on desired database in object explorer
- enter data-tier application
- select a package file
- you will see that the database name field has been updated to match the package file which should not be the case
Affected Area
- Connection dialog (SQL Server | Azure browse/Fabric browse)
- Query results panel
- Query editor
- Object Explorer
- Table Designer
- Schema Compare
- Schema Designer
- Local SQL Server Container provisioning
- SQL database in Fabric provisioning
- GitHub Copilot integration
- Query Plan Visualizer
- Other (please describe below)
If you selected "Other", please describe the affected area
Dacpac import and export
Environment Information
n/a
Confirmation
- I have searched existing issues and couldn't find a match
- I want to work on this issue