kbutti
1 year agoMicrosoft Employee
Status:
New
Workspaces cannot be associated to multiple Deployment pipelines
Currently we cannot associate one workspace to multiple deployment pipelines. If We have two workspaces with different sets of code and want to deploy to one Workspace that holds all code. It is not possible to create two deployment pipelines and deploy code from two workspaces into one. Use case: We have architecture where common/orchestration code sites in one workspace and deploy the code to any team's workspaces that want to utilize our orchestration code. With current product limitation, we cannot have multiple deployment pipelines created for each team and have common code workspace assigned to each pipeline.
1 Comment
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
Data Pipelines - Run only selected activities
For debugging and testing pipeline activities during development, allow us to select one or multiple activities and run only the selected pipeline activities. For example, I'm working on editing ...frithjof_v4 hours agoCommunity ChampionNew612Views11likes2CommentsSemantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connec...frithjof_v12 hours agoCommunity ChampionNew17Views1like0CommentsBulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change ...vishal14019716 hours agoFrequent VisitorNew6Views0likes0Comments