SQL Database connection now case sensitive?

[jcampbell474]

Have an app in the service that has reloaded daily, just fine/without issue.  Edited it yesterday in the Aug 2020 desktop release and republished.  It will not refresh - says that no gateway is available.  The gateway is available and used by other apps.  All connections were tested and they are fine.

I can refresh the app on my desktop.  Only thing I noticed is that the case sensitivity for one database was different in the pbix vs. gateway.  Changed it and reloading now - testing.

The reason I'm posting here is 1) because early this week, another user had a similar issue w/an on-prem app.  The report server would not refresh the app until he matched database cases in the PBIX with what was in the stored on the reporting server (he did a Replace of the app).  2) to see confirm/validate our suspicion - was this a change in one of the recent releases?  Are SQL databases case sensitive in the PBIX vs. Report Server & PBI Service Gateway?

[jcampbell474]

While we did recognize database case sensitivity w/an on-prem app, I don't think it's the culprit in this scenario.

I publish to the workspace and it immediately fails with the error shown, below.  I publish to a different workspace and it refreshes fine.  Using the same gateway cluster.  The only difference is the last datasource (2nd screenshot).  It has (the correct) options in the mapping dropdown, but when I select one - the apply button doesn't become enabled.  Why can't I map this datasource and why does it show a green check?

[GilbertQ]

Hi there

Because the data sources are defined in Power Query they are case sensitive.

For example if you have a PBIX where the SQL Server Name is: MyDatabaseServer

And you have a second PBIX where the SQL Server name is: mydatabaseserver

These will be seen as 2 different data sources.

To correct the issue both must have the exact same Server names.