When you click the elipsis next to an object in the Fabric browser interface and select "Save as" the behavior is dependent on the type of object you are copying.
If the object is a Dataflow Gen2 CI/CD, then after getting created IN THE SAME FOLDER AS THE ORIGINAL, it opens the object for editing.
If, on the other hand, the object is a Pipeline, Fabric opens BOTH the original object and the copy. And, oh, by the way, the new object is created in the ROOT folder, not the folder in which the original object resides.
I have not tested functionality for other object types Save As operation, but I bet there are at least two other variations of what happens.
Please be consistent!
No CommentsBe the first to comment
Recent ideas
Semantic 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_v5 hours agoCommunity ChampionNew10Views1like0CommentsBulk 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 ...vishal1401979 hours agoFrequent VisitorNew5Views0likes0CommentsAbout "Download SQL database project" and fix the downloaded project
1. The sqlproj must be fixed, it is downloaded without the xml markup line <?xml version="1.0" encoding="utf-8"> 2. The sdk must be updated: Actual: <Sdk Name="Microsoft.Build.Sql" Version="0.1...Jarrinf19 hours agoFrequent VisitorNew48Views3likes2Comments