Andy Brownsword changes a variable:
A regular Database Project deployment is static and delivers consistent results regardless of environment. When it comes to schema, that’s usually desired, but data is a different story.
Data is environment specific. You want a Database Project that works across all environments. You want smarter deployments. You need SQLCMD Variables.
These have been the go-to method for handling different environments and other things that change between releases since I started using database projects about 15 years ago. Looks like not a lot has changed on this front, but it’s good to see that they still work as expected.