Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Hi @Kiwi_Kyle ,
I did a simple test but it doesn't seem to reproduce what you have.
Are you using the latest version of Power BI Desktop, my test version is:2.126.1261.0 64-bit (February 2024)
Does this issue only occur in this report or can it be reproduced in New report?
Best regards.
Community Support Team_Caitlyn
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
Hi all,
This issue has been fixed,please try it again and thanks for your patience.
Best regards.
Community Support Team_Caitlyn
Hi @Jerzy ,
Can you provide 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 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 @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 @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 @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 @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 all,
This issue has been fix,thanks for your feedback and patience.
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
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
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
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 am so glad that your issue has been fixed . I will change the status to "Delivered" .
Best Regards,
Community Support Team _ Ailsa Tao
Hi @daaa ,
Please check if SSO is enabled. The Test as role/View as role feature doesn't work for DirectQuery models with single sign-on (SSO) enabled.
Through my testing, dq schema connection to sql server data source mixed with import schema of sql server's composite model, RLS takes effect. lc schema connection to power bi dataset then converted to dq schema and then mixed with import schema data source, RLS is not supported.
Refer: Row-level security (RLS) with Power BI - Power BI | Microsoft Learn
Use composite models in Power BI Desktop - Power BI | Microsoft Learn
Best Regards,
Community Support Team _ Neeko
Hi all,
I will update here if there is any progress, so please be patient.
Best regards.
Community Support Team_Caitlyn