Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi @Myrthe
We have seen on the internal platform that other engineers have reported this issue and submitted it.
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, so please be patient!
Best Regards,
Community Support Team _ Ailsa Tao
Hi @jdmontes
We have seen on the internal platform that other engineers have reported this issue and submitted it.
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, so please be patient!
Best Regards,
Community Support Team _ Ailsa Tao
Hi @rahulshevde ,
Sorry, but we couldn’t provide any support outside this post. There are several existing ICM(292502976, 294087216) related to WebView2 crash, and product group is investigating on such issue. Will follow up them and sync here once there is update. In addition, please make sure you are using latest version of Power BI Desktop and try different versions of WebView2 at the same time. Thanks in advance!
Best Regards,
Community Support Team _ Caiyun
Hi all,
This issue has been fix,thanks for your feedback and patience.
Best regards.
Community Support Team_ Caitlyn
Hi all ,
Issue has been solved by whitelisting https://content.powerapps.com
Best Regards,
Community Support Team _ Ailsa Tao
Hi @sebadb9 ,
We've seen that you've submitted support tickets, and ticket engineers have more authority to handle these issues than we do. Sorry for the bad experience, but the best way to address this issue at this stage is delete your dataset/report in the service and publish a new one. It’s by design.we see that you are not very satisfied with this solution and the product will continue to be optimized.
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 from ticket engineer.
Best Regards,
Community Support Team _ Caitlyn
Hi @all,
We reported the issue internally and got the following response from the PG team engineers:
Since this in preview feature,We do not allow some actions for this Preview features for now. This is a feature request for a new visual still under development.
Engineers are doing their best to optimize this preview feature, thanks for your feedback and support!
Best regards.
Community Support Team_Caitlyn
Hi @khacwee
We have seen on the internal platform that other engineers have reported this issue and submitted it.
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, so please be patient!
Best Regards,
Community Support Team _ Ailsa Tao
Hi all,
This issue has been fix,thanks for your feedback and patience.
Best regards.
Community Support Team_ Caitlyn
Hi @jaykayelsemicol ,
I tried again and still can't reproduce the problem, also haven't found ICM reported internally. If the problem persists, I suggest you create a support ticket, it's free for pro user and a dedicated engineer will come to dig the problem for you.
Best regards,
Community Support Team_yanjiang
Hi @is001902 ,
If the SQL Server is under heavy load or if there’s a long-running query, it might cause timeouts. You may try monitor the SQL Server’s performance and check for any slow-running queries.
Sometimes, spikes in the number of connections also lead to issues.You could try refreshing the credentials in the data source settings of the semantic model.
Best regards.
Community Support Team_Caitlyn
Hi all,
It's a known issue and there is no ETA now . As a mitigation meanwhile, please give user viewer permission to underlying workspace to allow them to create FRA.
Best Regards,
Community Support Team _ Ailsa Tao
Hi @kaylastarr ,
Seems the issue was resolved, please try again in your side.
Best regards,
Community Support Team_yanjiang
Update:
There has been internal feedback from engineers about this issue and it will be fixed in a future release, no definite ETA at this time.
Best regards.
Community Support Team_Caitlyn
Hi @N24PBI ,
Based on the Error “There is already a column with the name XYZ” ,it usually occurs when you’re trying to create a new column with a name that already exists in the table1. It can also happen if you have a reference to this column in some calculations within other datasets, causing other tables to also throw an error related to this column.
To resolve this, ensure that you change the name of this referenced column in all measures/calculated columns.
You may also refer to this thread:The name is already used for a column on table - Microsoft Fabric Community
Best Regards,
Community Support Team _ Caitlyn
Hi @roselilly23 ,
The issue is resolved in the new version 2.119.666.0 64-bit (July 2023).
Best regards,
Community Support Team_yanjiang
Hi @PrashantC ,
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 all,
This issue has been fixed. Please try it later.
Best regards.
Community Support Team_Caitlyn
We got feedback from PG team:
“The original issue (blank page) has been fixed and the Print functionality always had problem as we don't control the layout of the page and many times browser behave weirdly. That is the reason we added it in public documentation, "There are browser settings you can use to adjust the printout, but even then you still may not get the result you want. Consider exporting to PDF first and printing the PDF instead.”
Hi @stanxl
For more significant errors, they are available through this Support panel. This does not require permissions for the user.
Microsoft Fabric Support and Status | Microsoft Fabric
Best Regards,
Community Support Team _ Ailsa Tao