Changing data source "breaks" gateway settings

[MarkPalmberg]

Recently (last week or so) I've noticed that when I modify the data sources in a pbix (typically just adding an additional query from an existing SQL server/database in the report), my data refreshes fail after uploading the pbix to the server. When I look at my gateway settings, the new data source seems to be generating a duplicate data source in my gateway settings that I can't resolve any other way than having someone else take over the settings for the report. At this point, the gateway settings seem to "refresh," and things go back to normal (the duplicate data source goes away).

So, am I using the incorrect process for updating my reports in the service? I've just been overwriting my existing reports in the service, using the same name in the same workspace, etc., but clearly this isn't optimal.

Thanks for any tips you can pass along.

[jcampbell474]

I've had this happen, many times.  It makes no sense.  Actually had to open a ticket and the 'workaround' was to add the data source(s) to the gateway, again.  Everything matched, case sensitive, etc...  Tech support had no explanation.  

Seemed like it mostly happened after a (monthly) gateway upgrade.

Anyway, best of luck to ya.

[lbendlin]

Double (and triple) check the spelling of the connection details on the gateway and on the Power BI desktop.  Then check it again.  They need to match exactly, otherwise you end up with duplicate and unselectable gateway connections.

You can correct the issue on either side but the end result needs to be that the connection details match to the (case sensitive) letter.

[MarkPalmberg]

Thanks for this reply, @lbendlin. It's unclear to me how simply having another user take over the data souce settings (without changing any of the data source names) resolves this isse if case sensitivity/naming is really at fault, but at least we have a workaround.