With the advent of AI - it's becoming a lot easier to visualize data by quickly generating HTML pages using CoPilot, than it is to do this using Power BI.
It is time to stop insisting on the Workspace being included in a Fabric Capacity, to enable use of CoPilot in power BI.
Even when the workspace is in a Fabric capacity - the CoPilot agent can't "see" any of the data - only the schema - so it's a lot less useful than it really should be.
Even people who love Power BI are starting to code up web pages instead for near-instant visualizations - MS needs to make CoPilot more useful for Power BI Report Builders - and FAST.
Suggest:
For Power BI Workspaces: Let CoPilot in Power BI Work - with visibility limited to Schemas only.
For Fabric Workspaces/Semantic Models: Make CoPilot in Power BI talk to the Fabric Data Agents by default, to ensure it can actually see the data as well.
(It's also time to give Report Reader rights at something smaller than the F64 Capacity).
Recent ideas
Dynamic current-period defaults for separate Year and Month slicers
Scenario The target scenario is a report viewed in Power BI Service, using a DirectQuery semantic model and a dedicated Date dimension. Separate Year and Month slicers are part of the required user ...vvargasv12 hours agoMicrosoft EmployeeNew9Views0likes0CommentsAbout "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...Jarrinf18 hours agoFrequent VisitorNew74Views3likes3CommentsAdd REST API to Take Ownership of Fabric Pipelines
When using service account to automatically deploy Fabric pipelines from Dev workspace to upper environments, the owner of pipelines in target envionment remain unchanged. In some situations, per...VickyPeng22 hours agoRegular VisitorNew364Views5likes2Comments