Power BI is constantly evolving. But that evolution is poorly communicated. I usually find out about changes when I try to update or refresh data in a report and something breaks. I manage a SOX control that uses Power BI. It has to work, PERIOD! To open the desktop app or to open the report and find out some change has nerfed my report is terrible.
Oh well! We have to stay up to date with the latest security requirements. We have to enhance this, that and the other thing. GREAT! Make sure the changes are communicated and the transition managed so my reports don't break. Give me the path to moving to whatever the new requirement is insteand of simply breaking my current solution.
C'MON...users shouldn't find out about changes when they can no longer use their current version. We should be better than that.
Recent ideas
Add "Collapse all / Expand all" to the Queries pane in Power Query Editor
Hi Fabric Community, I suggest adding a "..." menu beside Queries(n])with Collapse all and Expand all. Current state: With many queries, every group and Helper Queries folder is expanded. My 8...DataVitalizer8 hours agoSuper UserNew9Views0likes0CommentsAdd Automated Pre-Upgrade Compatibility Assessment for Fabric Spark Runtimes
Microsoft Fabric should provide an automated compatibility assessment before a workspace, Environment, notebook, or Spark Job Definition is upgraded to a newer Fabric Runtime. Spark runtime upgra...mourakshit9 hours agoNew MemberNew5Views0likes0CommentsSupport Creator-Independent Managed Identity and Ownership Transfer for Fabric Operations Agents
Microsoft Fabric Operations Agents should support an enterprise identity and ownership model that is independent of the individual user who originally created the agent. Today, an Operations Agent r...mourakshit9 hours agoNew MemberNew4Views0likes0Comments