Connection Strings in Gateway/Datasets are CASE Sensitive and should NOT be.
Plese refer to this Forum post: Re: Can't Reuse Dataset/Gateway for Dataflow - Microsoft Power BI Community
It appears that when creating a Dataflow based on ODBC, the Connection String is CASE Sensitive. I can verify that , while creating a Dataflow, if I type something like MyODBC for the name, and "DSN=MyODBC" for my Connection String, that Power BI CONVERTS it to "dsn=MyODBC".
If I then do that a second time and enter the EXACT SAME VALUES, I get a Dataset named "MyODBC (2)" with a Connection String of "dsn=MyODBC".
If Connection Strings are CASE SENSIVE and Power BI cannot match "DSN=..." with "dsn=..." then DO NOT CHANGE THE CASE WHEN YOU SAVE IT!!!!
EITHER:
A) Make Connection String Case INSENSITIVE (so that "DSN" = "dsn"
OR
B) STOP CHANGING THE CASE on values I type in.
4 Comments
- AnonymousNot applicable
Hi ToddChitt
Can you provide the corresponding screenshots for clarification ?
Best Regards,
Community Support Team _ Ailsa Tao - ToddChitt
Super User
As stated in the first line of this issue:
Plese refer to this Forum post: Re: Can't Reuse Dataset/Gateway for Dataflow - Microsoft Power BI Community
Please read that post and look for my reply dated 10-18-2022 07:34 AM
There are screen shots there, with steps I took along the way. I cannot be any more clear than that.
Thank you.
- ToddChitt
Super User
Anonymous You flagged this as "NEEDS INFO". I have responded with a link to the original post where by I have explained everything in great detail, including screen shots. If you need info, please tell me WHAT info you lack as I thought the original post spells everything out very clearly.
Thank you.
- Jason_PlattNew Member
I am also encountering this issue, it is very annoying.
Using a self-hosted gateway (latest version), with an Oracle datasource.
In the PowerBI web portal, if you name connections in uppercase and the powerbi report that you are uploading specifies the connection name in lower case, it will *usually* fail. It doesn't always fail, and I'm not sure why.
The only workaround I've found is to name everything in lower case, from the TNS names entry, to the label, to the connection name.