Hi all,
This issue has been fixed. Please try it later.
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.
Workaround for now:
For the desktop a possible mitigation is to use the older version of the desktop.
In the service, the issue is specific to exporting to Csv format. A possible mitigation is to export to excel and the convert the file to csv.
I will update here if there is any progress, please be patient.
Best regards.
Community Support Team_Caitlyn
Hi @V_Ivanova ,
This issue has been submitted internally. Please be patient to wait for fixing. If there is any news, I will update it here.
After my testing, you can roll back to the July version of desktop or publish to service and then export the data in service and they work fine.
Best Regards,
Community Support Team _ Neeko
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 @AlexV00 ,
This is a known limitation of bookmarks as they stand now.
To ensure that we're consistent with the last-button clicked remains active regardless of other actions taken, this is expected behavior due to the noted behavior change. The bookmark navigator remembers the last button that was clicked.
The PG team is looking into planning an upcoming scenario that would fix this limitation.
Best regards.
Community Support Team_Caitlyn
Can you create a new report with Azure Data Lake Gen 2 normally ? Or does this problem occur in the specified report ?
Best Regards,
Community Support Team _ Ailsa Tao
Hi all ,
This issue has been fixed, please check your report and retry it!
Best regards.
Community Support Team_Caitlyn
Hi @Data-Rainer
Issue is mitigated in all regions except CANADA central. ETA for Canada is 19th . Please refresh the browser and check the dataformat .
Best Regards,
Community Support Team _ Ailsa Tao
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 @gopschennai
Thanks for your feedback ! Issue forums are used to deal with issue reporting or system bugs. If you have any requests for new features, you can mention your needs to the Ideas forum.
You can vote the idea and comment there to improve this feature. It is a place for customers provide feedback about Microsoft Office products . What’s more, if a feedback is high voted there by other customers, it will be promising that Microsoft Product Team will take it into consideration when designing the next version in the future.
Best Regards,
Community Support Team _ Ailsa Tao
Hi @fapomatius ,
This issue has been submitted internally. Please be patient to wait for fixing. If there is any news, I will update it here.
Best Regards,
Community Support Team _ Neeko
Hi @kaylastarr ,
Seems the issue was resolved, please try again in your side.
Best regards,
Community Support Team_yanjiang
Hi @gp10 ,
Thanks for the feedback, you are referring to this issue only occurring with Power BI Service, right?
Please check the version of Power BI Service you are currently using in About, as well as the browser you are using.
We'll get back to the product team as soon as it's acknowledged as an issue!
Best regards.
Community Support Team_Caitlyn
Hi @Nhigdon_ST ,
I can't reproduce your error." Does "Not allowed to save settings" mean a pop-up error message? You can try clearing your browser cache or accessing the PBI service in privacy mode and try again.
If you see the Apply Successful message in the upper right corner please wait fifteen minutes, the changes will not take effect immediately.
Best Regards,
Community Support Team _ Neeko
Hi @shabeer
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 fixed, please check your report and retry it!
Best regards.
Community Support Team_Caitlyn
Hi all,
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 @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.
This issue has been addressed and will be available in the next release of Desktop. No clearly ETA for now.
I will update here if there is any progress, so please be patient.
Best regards.
Community Support Team_Caitlyn
Hi @o59393 ,
I got the news that you have opened a surpport ticket.
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.
Best regards.
Community Support Team_Caitlyn