Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
2 years ago

Refresh via custom connector

Hello everyone,

 

I'm pretty new in the creation of a custom connector but I was able to build something which works in power bi desktop
Now, I would like to make some refresh online, so I follow the following tuto:
Custom Data Connector: How to Deploy and Test - Microsoft Fabric Community

 

my .mez files is well deployed on my server 

but once I'm in power BI Services, I click on discover data sources, it returns me the following error message

Unable to determine the data source. In order to determine details about custom connector based data sources, Power BI service needs to connect to a gateway, however, no gateway was available/reachable. Details: Static analysis failed in gateway. gatewayObjectId:<eupi>56c9746e-76ba-4d4a-a7e4-1228d3bcf9d5</eupi>, resultCode:FailedDueToGatewayUnreachableException Received error payload from gateway service with ID 1011315: [Expression.Error] We cannot convert a value of type List to type Text.. .

  • Data source for Query1

 

 

 Is it something wrong in my connector or in my datagateway? with the first part, I would think that the issue is my gateway but the second part make me think about an issue in the connector

 

So how can I debug that?

 

Many thanks in advance for your help 🙂

4 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    HI Anonymous ,
    Based on your description and the error message provided, first confirm that the Local Data Gateway is installed and running on a server that is always on and connected to the Internet. The gateway should be in a version that supports custom connectors. Then, make sure that the files are placed in a directory that is accessible to the gateway. Typically, the gateway service does not have access to user configuration files or folders under the system folder. Finally, in the Power BI service, ensure that the data sources that use the custom connector are properly configured in the gateway. This includes specifying the correct gateway in the dataset's settings.
    About We cannot convert a value of type List to type Text. error message. You can if you implement the TestConnection section in the custom connector code. Verify that the custom connector contains a function and that the function is implemented correctly. Of course, you can also look for any expressions or functions that involve data type conversions, especially from list to text. Make sure these conversions are handled correctly.
    You can check out these documents for more information on how to troubleshoot this problem
    Use custom data connectors with the on-premises data gateway - Power BI | Microsoft Learn
    TripPin 9 - Test Connection - Power Query | Microsoft Learn
    powerquery - We cannot convert a value of type List to type Text when importing XLSX file Power Query - Stack Overflow

    Best regards,
    Albert He

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

  • Anonymous's avatar
    Anonymous
    Not applicable

    Thank you for your help Anonymous 
    I tried what you suggest, but now I have another error message

     

    The credentials in power bi services are greyed out, and my custom connector is set on Anonymous authentification, so I do not understand why it returns the following error message 😕

     

     

    • Anonymous's avatar
      Anonymous
      Not applicable

      Hi Anonymous ,
      Based on your description and the error screenshot provided, you need to go and check if your gateway supports custom connectors.

      Best regards,
      Albert He

      If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

      • Anonymous's avatar
        Anonymous
        Not applicable

        Thank you for your help
        After investigation, I saw that the admins forgot to create a connection in power bi servies manage connection and gateways

         

        So the issue is probably coming from there 
        I keep you inform if it fixes the issue