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!
frithjof_v
on:
Job scheduler API: List failed runs
YSD
on:
Automated export for Eventhouse data to Lakehouse ...
on:
REST API for removing all tags