SharePoint credentials shouldn't be based on case sensitive URL

[madrid]

Hi there,

There were some issues reported about people getting problem with SharePoint credentials after takeing-over other's dataflow, or after importing dataflow (json) (*). I have the same issue and found out the issue is with condition:

"Each user can only have one set of credentials per data source, across all of the datasets they own, regardless of the workspaces where the datasets reside."

The problem is, even with the same source (SharePoint site), but if use has already establised the connection to the same SharePoint but different case sensitive then the they will get problem with source credentials.

I found that, saved credentials differentiate between:

https://company.sharepoint.com/sites/TeamA 

and https://company.sharepoint.com/sites/teama

At the moment, user should find every place in the import dataflow to change SharePoint source URL to match with URL they establised connection before. This could be time consuming and ineffective.

The Team please consider a better solution for this.

Thanks!

(*)

https://community.powerbi.com/t5/Service/Unable-to-update-data-source-credentials/m-p/2784860#M17378...

https://community.powerbi.com/t5/Service/Dataflows-problem-Validating-credentials-for-Sharepoint-sou...

https://community.powerbi.com/t5/Service/SharePoint-credentials-invalid-only-in-Service/m-p/2135568#...

[Anonymous]

Hi @madrid ,

If you would like to suggest some feature improvements. I have found users with similar needs to you here

 Ideas (powerbi.com) , you may vote the idea and comment  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 Selina zhu