This happened to me also once recently on SSMS version 17.9.1.
This issue was recently fixed in our internal branch. The fix will be included in the next major version of Visual Studio (i.e. 2019)
Any news on when the update will be released? This breaks our automated builds whenever we change master.dacpac references. We also have a mix of developers running Professional and Enterprise editions, so local builds fail.
168 votesstarted · 15 comments · API Management » API management experience · Flag idea as inappropriate… · Admin →
Allowing subscriptions and keys to *not* be associated with any users or groups at all is an important scenario. We would like to programmatically create subscriptions and keys, and display the keys in another web application that is acting as a frontend to API Management. Users of the frontend will ideally have no knowledge that we're using API Management on the backend.
This is partially implemented now as of 7/9/2018. However, we've noticed that if you deploy a dataset or pipeline using VSTS from Git, them the folder names on the object are not persisted in the Data Factory. It seems like this must be a bug.
1. We're deploying our changes to Dev. We check-in from the Data Factory UI to a feature branch, and merge to our dev branch. A VSTS release is kicked off when we merge to dev. That release run an ARM task to deploy the Data Factory resource.
3. We trying to make the release consistent between all environments (dev, stage, prod), and also re-deployable in case we want to create a new dev environment. If we do happen to want to make a change to the Data Factory resource, we do not want to make temporary changes to the release or disable tasks in the release.
It would be very useful to be able to export with PowerShell, rather than copy and paste via the Code view.