PowerBi Service - Workspace folder name validation doesn't consider case

[bhalicki]

When I try and change the name of a folder in a workspace in PowerBi service, the UI validates that the folder exists, but doesn't consider case.

For example: I have a folder called "Semantic models" and I want to change this to "Semantic Models".  I get the following error:

[Anonymous]

Hi  @bhalicki ,

If the workspace name change has disrupted the connection to your dataset, you will need to manually reconnect to it. In Power BI Desktop, go to Home > Transform Data > Data source settings, find the source that's causing the issue, and update the connection information to reflect the new workspace name.
After updating the connection information, try refreshing both datasets in Power BI Desktop. This can help re-establish the connections and ensure that the datasets are up-to-date.
Once you've successfully reconnected to the dataset and refreshed the datasets, save your report and re-publish it to the Power BI service. Make sure to publish it to the workspace with the updated name.

Hope it helps!

Best Regards,
Community Support Team _ Caitlyn

[bhalicki]

Hi Caitlyn, I'm really sorry, but I think you may have misunderstood my issue. When I log into PowerBi Service and create a folder, then try to rename the folder by changing the case only, it says that the folder already exists. For example, if I create a folder "hello" (all lower case), then rename this folder to "Hello" (with the first letter capitalized), PowerBi Service says I need to choose another folder name as this folder name already exists. I think the code behind the GUI is checking the folder name, ignoring the case. Thanks, Ben.

[bhalicki]

Hi @Anonymous , can you please change the status of this issue, because it has not been delivered.

[bhalicki]

Hi guys, I am raising a ticket internally for this. The folders functionality is broken. If I create a new, empty folder and publish a report from PowerBi desktop, it often says that the report already exists (when it doesn't, in that folder). What's worse, sometimes I publish a report to a folder and it doesn't ask me to overwrite the existing report, instead creating a duplicate in the same folder. This creates a huge mess, as I have to delete the old report, publish a new one, then reconfigure the app, menu structure, security etc associated with the report. Hope this is fixed soon, it is becoming very frustrating to work with. Thanks, Ben.