Issues with Gateways, Source already existent but it continues to request it to be added

[Joorge_C]

Seeing multiple issues with Gateways about that have started about a week ago. Please see this one, it appears there is a Bug.... This source was already working, but now it shows as if it needs to be added to the gateway. Once added again with a new name in source it will continue to show in gateway as if it needs to be added from sctratch. BUT this source had been here all along. Tested in 2 separate gateways. Source is an Excel file hosted in Sharepoint. 

[v-binbinyu-msft · Accepted solution]

Hi @Joorge_C ,

This is acknowledged as an issue. We have reported the issue and submitted it to the internal icm platform, No: 360525736. Engineers will do their best to resolve the issue. I will update you here if there is any progress , please be patient.

Best regards,
Community Support Team_Binbin Yu

[LJCFPL97]

Is there anyway to check for updates on this issue to when it is resolved, having the same issue myself. Thanks

[lbendlin]

The issue persists, and it boils down to a disagreement on the connection string between the dialog that asks you to create the connection and the dialog that creates the connection (the latter omits the trailing forward slash that the former expects).  Short term remedy is to manually create the connection including the trailing forward slash.

[vckbx]

Can you explain what you mean by "Short term remedy is to manually create the connection including the trailing forward slash."?

[lbendlin]

let's say you have a web data source at https://website.com  .  In the gateway connections dialog for the dataset you will be asked to add "https://website.com/" to the gateway.  When you click on "Add gateway"  the gateway connection creation dialog will prepopulate "https://website.com" .  If you create the connection like this it will result in the endless loop behavior you experience.  Instead, manually change the connection source to "https://website.com/"  before hitting "Create".  Then the connection will be mappable.

[LJCFPL97]

Thanks, I cam confirm this solved the issue

[lbendlin]

It's not a solution, it is only a workaround. A true solution will be to synchronize the service dialogs.

[sunshine_1234]

Hello All, I have the same issue... "Add to gateway" is not an option anymore... 

I noticed this behaviour from the beginning of this year... 

Thanks

[lbendlin]

You do not need to use a gateway for Microsoft cloud data sources (like your sharepoint list)  UNLESS you are merging that data source with an on-prem data source in Power Query (which you shouldn't do anyway).

The "Add to gateway"  is only a suggestion, it is not required.

[Joorge_C]

Thanks @lbendlin  the issue is the Gateway is grayed out and cannot be selected, possibly due to that the same message of 'add to gateway' continues within the Sources listed. You can see from my screenshot it cannot be selected.