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 all ,
I searched for recent known issues and didn't find anything similar. So I need more information to confirm and restore this issue. Are you guys able to restore this issue on the latest version (by creating a similar report instead of opening the previous one directly). Or provide a simple pbix file to prove this issue?
How to provide sample data in the Power BI Forum - Microsoft Fabric Community
Best Regards,
Community Support Team _ Ailsa Tao
Hi @Kiwi_Kyle ,
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.
The fix will be deployed in the May release.
I will update here if there is any progress, so please be patient.
Best regards.
Community Support Team_Caitlyn
Hi all,
This issue has been fixed,please try it again and thanks for your patience.
Best regards.
Community Support Team_Caitlyn
Hi @Jerzy ,
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.
The fix will be deployed in the May release.
I will update here if there is any progress, so please be patient.
Best regards.
Community Support Team_Caitlyn
HI all,
The PG team is still working on this and I will update the status if there is any progress. The current workaround is a rollback to the December 2023 version. Thank you all for your cooperation!
Best Regards,
Community Support Team _ Ailsa Tao
Hi @QC
It's a known issue . There is no specific time frame for the fix yet. You can temporarily solve your problem with the following workaround. The same effect can be achieved with the DAX Query View .
Best Regards,
Community Support Team _ Ailsa Tao
Hi @cperuski
It’s a known issue . The engineers are actively working on this issue and I will come back with an update if there is any progress.
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 all,
This issue has been fix,thanks for your feedback and patience.
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 @Cristian_Alzate ,
Can you provide the 2 detailed version information so we can reproduce the issue? We'll get back to the product team as soon as it's acknowledged as an issue!
Thanks in advance!
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
Update:
The issue is already fixed in all regions and clusters. A fix on this issue will be available around the mid-September release.
As a workaround for Power BI Dekstop for now, Customers can add the ID column back to the select statement within the M Query if customers are using ID column in "Table.SelectColumns" - Customers can remove the ID column within the M Query if customers are using ID column in "Table.RemoveColumns"
Best regards.
Community Support Team_Caitlyn
Hi all,
Based on user feedback, updating to the latest version of Power BI solves this problem.
Best regards.
Community Support Team_Caitlyn
Hi @ali_b
No one else has yet responded with the same problem. So it's not possible to tell if it's a generalized problem caused by a version update. You can download the previous version in the link below .
Previous monthly updates to Power BI Desktop and the Power BI service - Power BI | Microsoft Learn
If going back to an older version solves the problem, then something changed in the new version that may have caused the problem.
Here is the new features about Power BI February 2024 update .
Power BI February 2024 Feature Summary | Microsoft Power BI Blog | Microsoft Power BI
Best Regards,
Community Support Team _ Ailsa Tao
Hi,
There is a Service Outage/Degradation mentioned on the support page of the Power BI, so stay tuned:
https://powerbi.microsoft.com/en-us/support/
I will update here once I get any information.
Thank you very much!
Best Regards,
Community Support Team _Robert Qin
I found a document related to connecting to SharePoint using service principal that you can refer to. Hope this will help you.
How to connect SharePoint online using service principal? - Microsoft Q&A
Best Regards,
Community Support Team _ Ailsa Tao
So you created a dataflow via lakehouse ? Can you describe your procedure in detail?
Best Regards,
Community Support Team _ Ailsa Tao
Hi all,
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_Caitlyn