Imagine having a left vertical page navigator with big icons instead of plain page names and being able to scroll through those if have too many pages, at the same time some fixed icons just below it (may be a horizontal parting line) making it half dyanamically scollable and half static icons for bug, archives actions etc. For most of our reports we have more than 5 to 8 pages, then we also have bug, archieve buttons as well, for all we use buttons as we use icons and assign actions of page navigation, I know this sounds like page navigator, but page navigator does not allow to have images (which represents the page info) to be added instead of name (I know we can add char icons but they are of no use), so I would like to see images could be added instead of text in page navigation, wherever Icon is not enabled, page name would appear.
... View more
Updating the Mashup.pq is actually something that would trigger a commit and not something that we would recommend as it woudl be considered a change between the Dataflow that you have across workspaces.
Fundamentally, you want the same Dataflow definition across all environments, but they should have the right context as to what items they should be getting the data from OR loading the data to.
The article below explains in detail with tutorials how you can set the best solution architectures with a Fabric deployment pipeline in mind:
CI/CD and ALM solution architectures for Dataflow Gen2 - Microsoft Fabric | Microsoft Learn
Do feel free to post any other ideas if you think that there's any functionality that should be extended or improved on