Bug Report: Invalid Perspective Definition Prevents PBIP Model from Loading in Power BI Desktop Issue Description When a developer renames measures that are included in a perspective within a PBIP model, Power BI Desktop fails to load the PBIP file. The error message is generic and does not specify which measures are invalid in the perspective. Since Power BI Desktop does not support perspectives, an invalid perspective definition should not prevent the PBIP model from loading. Steps to Reproduce Open Tabular Editor and define a perspective in a PBIP model, adding several measures to it. Rename one or more of the measures that are included in the perspective. Save the changes and attempt to open the PBIP file in Power BI Desktop. Expected Behavior Power BI Desktop should still load the PBIP model, even if a perspective contains invalid references. If an error occurs, the message should clearly indicate which measures are invalid in the perspective. Actual Behavior Power BI Desktop fails to load the PBIP file. The error message is generic and does not specify the problematic measures. The only way to resolve the issue is to manually edit the perspectives.tdml file. Proposed Fix Allow PBIP models to load in Power BI Desktop despite invalid perspective definitions. Improve the error message to indicate which measures are causing the issue. ... View more

Currently, when setting the privacy level, it is necessary to manually set it for each data source every time. Therefore, I would like to use a feature that allows it to be turned on by default.  Understand Power BI Desktop privacy levels - Power BI | Microsoft Learn ... View more

Hello,   Allow to Change the length of the card visual based on the % it has. It will alllow it be used as chart with more formatting options.   Allow drill through to multiple pages simultaneously based on the option selected in drill down field. ... View more

I would like to be able to apply colors to pages in power bi desktop. Thus, I could organize my pages when I'm working on them ... View more

In Power BI workspaces, users currently need Contributor or higher permissions to publish reports. However, this grants them access to all reports, datasets, dashboards, and dataflows in the workspace, which may not be desirable in shared environments.   Proposed Solution: I propose introducing a "Publisher" role that allows a user to: ✅ Publish reports, datasets, dashboards, and apps ✅ Manage (edit, update, delete, and share) only their own published content ❌ Not access or modify content published by others ❌ Not manage workspace settings or permissions ❌ Not delete or modify datasets that they did not publish   Benefit: This role would enhance security and organization within shared workspaces, limiting visibility to only the reports a user publishes while still allowing contributions. It would be particularly useful in enterprise environments where multiple users publish reports but should not interact with each other’s work. Improves data security by preventing unauthorized access to other reports. Encourages collaboration while maintaining proper content ownership. Prevents accidental modifications or deletions of others' content.   ... View more

It's strange that we can easily show YoY changes on reference labels but not on the overall callout value.   ... View more

Hello Team, I want to inform you that we have noticed an issue with Power BI services. When we mark a report as confidential with a sensitivity label, it does not automatically apply when exporting the report to PPT. Please make the necessary changes to ensure that if a report is marked as confidential, the sensitivity label continues when exporting to PPT. Thank you ... View more

When running an "SELECT ... INTO" or "CTAS" query, the command fails: CREATE TABLE TESTTABLE AS SELECT JSON_VALUE(x, '$.test') as x FROM (SELECT '{"test":"test"}' as x) as u   You have to wrap each JSON_VALUE function, or other functions returning an nvarchar with a CAST/CONVERT to not get this error. Since the nvarchar data type does not exist for tables since they're always stored the same, please just convert it for us on the go. ... View more

Introducing the capability to apply two distinct themes within a single Power BI report, with a seamless toggle feature for users, would significantly enhance accessibility and user experience. Users could switch to a high-contrast theme with accessible fonts, catering to those with visual impairments. Additionally, different user groups could select themes aligning with their preferences or corporate branding, thereby boosting engagement and satisfaction. ... View more

Currently, Power BI does not support dynamically executing DAX formulas stored as text in a table.   When using LOOKUPVALUE to retrieve a formula, it is treated as plain text rather than an executable measure. This limitation prevents dynamic measure creation and forces users to manually define multiple measures using SWITCH, which is not always feasible.   I propose a feature that allows Power BI to evaluate and execute DAX expressions stored as text within a table column. This would enable users to define formulas globally and reference them dynamically in measures, eliminating redundancy and improving maintainability. Why This Matters: No Dependency on SWITCH – Useful in scenarios where SWITCH is impractical. LOOKUPVALUE Can Return Executable Measures – Avoids the issue of text conversion. Centralized Formula Management – Define formulas once and reuse dynamically. Greater Flexibility for Dynamic Reporting – Simplifies complex use cases.   This enhancement would significantly improve Power BI’s flexibility and efficiency for dynamic calculations. ... View more

Having the ability to assign tasks is great (Get data, Store, Visualize).  However, it would be great to group those tasks by a workflow name (or sub-workflow).  This would allow filtering options which would generate a list of tasks that are associated. ... View more

When creating a shared workspace in Power BI, we would like the initial display settings to be unified for all users. Specifically, we want to hide the task flow and the columns for "Task," "Approval," and "Confidentiality" in reports and folders. We would like these elements to remain hidden automatically when other members view the workspace for the first time. ... View more

When we create a dataflow Gen-1, we create a new gateway if one is not available. In this case, the person who created the gateway will be the owner of that gateway, and we won't be able to add anyone else to it, not even the person who created it. Ideally we should be able to update "manage users" in gateway? created via Workflow Gen-1 ... View more

Workspace name prefix as "DepartmentName" by default when user trying to create workspace in Power Bi Service? Ex: FIN - Quaterly Reports. FIN should be default to the Finance team users and next whatever the user wanted to name the workspace?   ... View more

This week, when doing some research, I opened the Fabric Warehouse pane on the left to check out the available DMV's and DMF's. As I was scrolling through the lists, I found that these were not ordered by name. This made searching for what I was looking for much harder, especially as intellisense wasn't helping me (it didn't do anything at that point in time).   It would be a massive help if these were sorted alphabetically the way it is with SQL Server combined with SSMS. ... View more

Since Fabric already has unified data layer OneLake - we could enhance the Bronze-Silver-Gold with additional Platinum layer with dynamic semantic relationships across datasets! Concept: Users should be able to create a dynamic, interconnected model of data relationships within an organization's data ecosystem. It represents data as: Objects: Real-world entities like equipment, products, or transactions Properties: Attributes of these objects Links: Relationships between objects It automatically maps data relationships across all Fabric workloads - empowers all users, regardless of technical skill with low/no code interface, to easily discover connections and insights within the data. (similar to Palantir's Ontology)  By dynamically linking data across touchpoints, this enables a comprehensive view of the data journey for MSFT's customers, informing strategic insights reactive to changing market trends. Further next steps: We could progress further and implement an AI-driven ontology that automatically maps and updates relationships between data entities. This layer continuously evolves based on data interactions, user behavior, and ML insights without reinventing the wheel for every usecase. This feature will not only match Palantir's ontology capabilities but exceed them by leveraging Microsoft's vast cloud infrastructure and AI expertise as it can accelerate time-to-insights by automating complex data relationship discovery! ... View more

Being able to create a trial for those of us who do not have access to a corporate account or it is not enabled. This way we have the possibility of training ourselves with this incredible platform ... View more