Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for a $400 discount.
Register nowGet inspired! Check out the entries from the Power BI DataViz World Championships preliminary rounds and give kudos to your favorites. View the vizzies.
Hi @VAMI ,
If Power BI Desktop is frozen, you may check that:
Best Regards,
Community Support Team _ Caitlyn
Hi all,
I'm glad you found workaround and shared it, for those of you who have had similar experiences check out the comments below.
Best regards.
Community Support Team_Caitlyn
Hi @Marko1992 ,
Based on the above information, It's a reproducible issue. Due to the new reply policy, I would suggest opening a Support Ticket.
If you are a Power BI Pro or Fabric licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you.
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.
The link of Power BI Support: Support | Microsoft Power BI
For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community
Best Regards,
Community Support Team _ Caitlyn
Hi all,
Yes, there is no clear solution about this issue yet. PG team suggests users to roll back to previous November version first, sorry for the inconvenience.
Best Regards,
Community Support Team _ Caitlyn
Hi @garynorcrossmmc ,
I tried to reproduce your issue but was unsuccessful, can you provide more information for us to investigate further?
What data source are you using? What is the connection mode? Are you using the latest version of Power BI Desktop (please note that it is the official download link version and not the MS app store version).
Best Regards,
Community Support Team _ Caitlyn
Hi @GM_AZ ,
Based on the above information, this issue is complex which may need to collect log files for further troubleshooting. Since community support engineers don't have that access, I would suggest opening a Support Ticket. If you are a Power BI Pro or Fabric licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you.
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.
The link of Power BI Support: Support | Microsoft Power BI
For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community
Best Regards,
Community Support Team _ Caitlyn
Hi @pinellus ,
Based on the above information, It's a reproducible issue. Due to the new reply policy, I would suggest opening a Support Ticket.Ticket support engineers will take your issue back to the PG team.
If you are a Power BI Pro or Fabric licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you.
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.
The link of Power BI Support: Support | Microsoft Power BI
For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community
Best Regards,
Community Support Team _ Caitlyn
Hi All,
These problems arise by design. As mentioned in the public documentation, USERELATIONSHIP cannot be used when defining row-level security for tables containing metrics, and CROSSFILTER is not supported in DirectQuery mode when used in computed columns or row-level security (RLS) rules.
USERELATIONSHIP function (DAX) - DAX | Microsoft Learn
CROSSFILTER function - DAX | Microsoft Learn
To resolve this issue, CROSSFILTER and USERELATIONSHIP can be removed from their metrics.Alternatively, the relationship can be modified as suggested by the public documentation of the RLS model.
Best regards,
Albert He
Hi @NarWind ,
Based on the above information, this issue may need to be addressed further. Since community support engineers don't have that access, I would suggest opening a Support Ticket. If you are a Power BI Pro or Fabric licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you.
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.
The link of Power BI Support: Support | Microsoft Power BI
For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community
Best Regards,
Zhu
Hi @NarWind ,
Based on the above information, this is a reproducible issue. I would suggest opening a support ticket and the ticket support engineer will feed this back to the product team for further investigation.
if you are a Power BI Pro or Fabric licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you.
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.
The link of Power BI Support: Support | Microsoft Power BI
For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community
Best Regards,
Community Support Team _ Caitlyn
Hi all,
Based on the above information, It's a reproducible issue. Due to the new reply policy, I would suggest opening a Support Ticket.
If you are a Power BI Pro or Fabric licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you.
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.
The link of Power BI Support: Support | Microsoft Power BI
For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community
Best Regards,
Community Support Team _ Caitlyn
Hi @TheDataBrick ,
Based on the latest update from our internal team, the fix is currently scheduled for March 24, 2025. In the meantime, I will keep you updated on any further developments or changes. Please don’t hesitate to reach out if you have any questions or need additional assistance.
Best Regards
Hi all,
I'm glad you found workaround and shared it, for those of you who have had similar experiences check out the comments below.
Best regards.
Community Support Team_Caitlyn
Hi @Idrissshatila ,
According to my investigation, Power BI is now running smoothly, please try it again.
Best Regards,
Community Support Team _ Caitlyn
This is already fixed, will be part of the March release of Desktop. Fix may reach the web sooner, possibly in 1 week. Please check back on 3/17 and let us know if things are working as expected in the web.
As this is in Preview, capabilities are being released incrementally. Some formatting features were not enhanced to support per-Category conditional formatting when we initially released Small Multiples. Note: we are changing the labels to align better across the product. Small Multiples is reserved for a third dimensional grouping. First is category, then series, then small multiples. Since this is a primary grouping, we will rename it "Categories" for consistency.
Hi all,
Based on the above information, It's a reproducible issue. Due to the new reply policy, I would suggest opening a Support Ticket.
If you are a Power BI Pro or Fabric licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you.
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.
The link of Power BI Support: Support | Microsoft Power BI
For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community
Best Regards,
Community Support Team _ Caitlyn
Hi @ccampora ,
We checked internally and found this to be an acknowledged issue.
The engineers on the product team are now aware and will do their best to resolve the issue. I will update here if there is any progress. Thanks for your patience.
Best regards.
Community Support Team_Caitlyn
Hi all,
This issue is fixed, please try it again. Thanks for your patience.
Best Regards,
Community Support Team _ Caitlyn
Hi @santhoshkj ,
The two users above have provided excellent responses, please follow the MS monthly updates to see the latest progress, thank you~!
Best regards.
Community SupportTeam_Caitlyn