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
Deployment Pipelines - Remember selected stage
Every time we go into a deployment pipeline, it defaults to selecting the Development stage. I believe that it would be very rare to have a user select the Development stage. It would be helpful if d...PeterDaniels1 hour agoAdvocate IINew1View0likes0CommentsDisable auto-restore previous session's tabs in new Fabric sessions
Description: Since a recent update, starting a new Fabric session — for example by opening Fabric in a new browser tab — automatically reopens all the item tabs that were left open from a previous s...MathieuVr8 hours agoFrequent VisitorNew56Views5likes1CommentExported PDF from PowerBI to not have any indents/borders
Currently, using the "Export to PDF" option in PowerBI results in two consistently buggy results: A white border/indent is generated, increasing the size of the page from 8.5x11 to 9x11.5 Sometime...EliShalev11 hours agoNew MemberNew12Views0likes0CommentsAdding a Container for Logical Grouping of Activities in Data Pipelines
Dear Team, I would like to propose a feature enhancement for Data Pipelines in Microsoft Fabric that allows the logical grouping of activities into a container. This container would serve to: Im...lukas_karlovsky12 hours agoNew MemberPlanned876Views15likes5Comments