Facing issue while deploying custom connector on Power Bi workspace

[Yuga]

Hi,

I have deploy custom connector on power Bi workspace so for that I performed below steps after 

1.I have installed "On-Premises Data gateway"

2.Gave the path of folder in connector section.

3. Then I went to power Bi workspace >>setting>>manage connections and gateways>>Click on New

4.I fill the details but for connection type my connection name(Which is AOT) is not poping up .

Please suggest on the above issue as soos as possible.

Or if there is any other to deploy custom connector please guid.

Thanks,

Yuga Pikalmunde

[Anonymous]

Hi  @Yuga ,

Please follow the thread below:

Use custom data connectors with the on-premises data gateway - Power BI | Microsoft Learn

Also please note:

• Make sure the folder you create is accessible to the background gateway service. Typically, folders under your users' Windows folders or system folders aren't accessible. The on-premises data gateway app shows a message if the folder isn't accessible. This limitation doesn't apply to the on-premises data gateway (personal mode).

• For custom connectors to work with the on-premises data gateway, they need to implement a TestConnection section in the custom connector code. This section isn't required when you use custom connectors with Power BI Desktop. For this reason, you can have a connector that works with Power BI Desktop, but not with the gateway. For more information on how to implement a TestConnection section, see TestConnection.

• If your custom connector is on a network drive, include the fully qualified path in the on-premises data gateway app.

• You can only use one custom connector data source when working in DirectQuery mode. Multiple custom connector data sources don't work with DirectQuery.

Best regards.
Community Support Team_Caitlyn

[Yuga]

Hi Team,

I have already followed the thread which you have shared. 

On-Premise Gateway is able to access the folder and name is coming up there in on-premise gateway as shown in attached screenshots in my description of the issue in the last comment. 
Also I have used TestConnection code as well according to the given template by you. Still i don't see this connection type in the LOV when i try to create connection through this gateway. 

So i have created .mez file through Visual Studio 2019. I have three parameters in my code URL, token and body. So in VS, when i execute my code, In the credential section i can see some characters which are getting added in the url section. For example, If I will pass "https://www.google.com/results" as url, in the datasourcepath field, it shows it as url: "https:\/\/www.google.com\/results",token:"passed token",body:"passed body". This is how it is building the datasourcepath field. So before every "/" VS is adding up one "\" I don't know why it is happening, may be VS is handling this special character escaping differently. not sure. This seems to be an issue as url is getting changed to something else. Please help on this. 

Another potential issue could be datasourcepath should come as AOT but its taking the concatenation of all the inputs passed. For example url: "passed url",token: "passed token", body:"passed body" . So We do not create this DataSourcePath field anywhere in the code logic. So how this DataSourcePath field is getting created internally through VS. This is my another question. Please help on this as soon as possible. 

Regards,

Yuga

[Yuga]

Please reply.

[Anonymous]

Based on the above information, if you are a Power BI Pro licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you.
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.

The link of Power BI Support: Support | Microsoft Power BI

For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community

Best Regards,
Community Support Team _ Caitlyn