Forum Discussion

scottdigs's avatar
scottdigs
Frequent Visitor
4 years ago
Solved

Paginated Reports: ODBC Data Source Connection String Is Not Supported

I'm trying to use Paginated Reports (on Premium Per User license) to connect to Snowflake. It works as expected when I connect to Snowflake via ODBC connection on both my personal machine and also on the server where the gateway is installed. Yes, I downloaded Report Builder on the server with the gateway to test the connection. 

 

The issue comes when the report is published to the web service.

After publishing the report, I go to manage the data source credentials and setup the connection to the gateway:

I go through the steps of adding an ODBC source, but I get the error that the connection string is not supported.

 

The above string matches Microsoft's documentation here: https://docs.microsoft.com/en-us/power-bi/paginated-reports/paginated-reports-odbc-support  and it did not work. I've tried several different connection string variations (w/ and w/o curly brackets, wrapping the string in double quotes, using DNS=... instead of full string, etc...) with no success.

 

I also tried using "Snowflake" as the data source type instead of "ODBC" since it is available in the drop down, but the web service doesn't allow for it to be mapped to the report for some reason.

 

Any ideas?

  • There's a solution! There's two workflows for adding data sources and the one I shared above has an issue. The scenario that worked was to go directly to the managed gateway settings and add a new data source and follow the steps for adding an ODBC connection. Screen shot is below. Afterwards, I published the report using the same connection string with success.

    Thank you bradsy  and GilbertQ for providing input on this.

     

7 Replies

  • scottdigs's avatar
    scottdigs
    Frequent Visitor

    There's a solution! There's two workflows for adding data sources and the one I shared above has an issue. The scenario that worked was to go directly to the managed gateway settings and add a new data source and follow the steps for adding an ODBC connection. Screen shot is below. Afterwards, I published the report using the same connection string with success.

    Thank you bradsy  and GilbertQ for providing input on this.

     

    • Kasia29's avatar
      Kasia29
      Frequent Visitor

      scottdigs which string connection variation worked for you? I'm having the same issue I tried dsn= but getting errors. Would you mind sharing?

      • bradsy's avatar
        bradsy
        Microsoft Employee

        You might want to contact support. I was also getting the same error when I tried to create ODBC with snowflake. I know it was working in the past, as I see existing ODBC snowflake on our gateway