Web V2 connection problem

[Pronocalme]

Hello everyone !

I've created a dashboard using a data source from an advanced Web connection, but when I publish this dashboard, the connection becomes a Web connection (and not Web V2 as it should be), so I can't enter a Bearer token and my connection is in error. Do you know how can I solve this issue ?

Thanks !

[v-hashadapu]

Hi @Pronocalme , Hope your issue is solved. If it is, please consider marking the answer 'Accept as solution', so others with similar issues may find it easily. If it isn't, please share the details.
Thank you.

[Pronocalme · Accepted solution]

Hello,

I recreated my report from scratch and my problem solved itself, without any change in PowerQuery. Thanks for the help !

[v-hashadapu]

Hi @Pronocalme , Hope your issue is solved. If it is, please consider marking it 'Accept as solution', so others with similar issues may find it easily. If it isn't, please share the details. Thank you.

[Pronocalme]

Hello,

Thank you ChatGPT and Ibendlin for your replies but it still doesn't work, I can't specify in PowerBI desktop that I want to use a Web V2 connection.

Here is my query :

let
Source = Csv.Document(Web.Contents(
"my-api-endpoint",
[
Headers = [
Authorization = "Bearer " & BearerToken
]
]
),
[Delimiter=",", Columns=9, Encoding=65001, QuoteStyle=QuoteStyle.None])
in
Source

[v-hashadapu]

Hi @Pronocalme , thank you for reaching out to the Microsoft Fabric Community Forum.

Sorry to know it isn’t working. Please consider below steps to ensure you are using a Web V2 connection.

1. In Power BI Desktop -> Go to Transform Data -> New source -> web -> Choose Advanced.
2. In the "Advanced" settings, ensure that you select "Web V2" as the connection type. If you do not see this option directly, it might be configured within the API key or authentication settings.
3. Enter your API endpoint URL in the "URL parts" section.
4. Select ‘Add header’ -> Select Authorization in Dropdown (type it in if it's not listed).
5. Click "Done" to apply the query.

Power Query Web Connector - Microsoft Learn

https://learn.microsoft.com/en-us/powerquery-m/web-contents

If this helps, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details.
Thank you.

[lbendlin]

2. In the "Advanced" settings, ensure that you select "Web V2" as the connection type. If you do not see this option directly, it might be configured within the API key or authentication settings.

News to me, and not supported by your screenshot.  Are you using a prerelease version?

[v-hashadapu]

Hi @lbendlin, Thanks for your reply. Apologies for not explaining it clearly.

As of October of 2021, Power BI Desktop uses Microsoft Edge WebView2, by default, for OAuth authentication for all connectors. so, i can't share a screenshot showing me selecting Web V2. But as i am not sure which version @Pronocalme is using, i gave two ways to ensure Web V2 is used. 

Please refer the below documentation:

https://learn.microsoft.com/en-us/power-query/oauth-edge-chromium

Thank you. 

[Pronocalme]

Thanks for your reply. Can you please tell me how to select "Web V2" as the connection type as you said there :

"In the "Advanced" settings, ensure that you select "Web V2" as the connection type. If you do not see this option directly, it might be configured within the API key or authentication settings."

[v-hashadapu]

Hi @Pronocalme , thank you for reaching out to the Microsoft Fabric Community Forum.

Please consider below:

1. Ensure that you are using the correct connection type. When setting up the connection in Power BI, make sure you select "Web V2" instead of just "Web”.
2. Try recreating the Web V2 connection from scratch. Go to "Get Data" > "Web" > "Advanced" and ensure you select "Web V2" as the connection type.
3. When setting up the Web V2 connection, ensure you have the correct URL and headers, including the Bearer token. Double-check the token and ensure it is valid.
4. When publishing the report, double-check the publish settings to ensure the connection type remains as Web V2.
5. Ensure that you have the necessary permissions to use the Web V2 connection and that the API endpoint you are connecting to supports Web V2.
6. If your Bearer token is dynamic or sensitive, consider using a Tableau parameter to store and manage it securely. This parameter can then be used within the Web V2 connection string.
7. Verify that your Tableau Server environment is configured correctly to support Web V2 connections and any required authentication methods.
8. Review the Tableau Server logs for any error messages related to the Web V2 connection or the published workbook.
9. Make sure your Power BI Desktop is up to date. Sometimes, updates include fixes for such issues.

If this helps, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details.
Thank you.

[FarhanJeelani]

Hi @Pronocalme ,

The issue you're facing with the Web V2 connection reverting to a basic Web connection in Power BI Service is common when using advanced Web connections with custom headers or Bearer tokens. Here's how to resolve it:

Solution:

1. Use a Parameter for the Bearer Token:

   • In Power BI Desktop, create a parameter to hold your Bearer token (e.g., BearerToken).
   • Use this parameter in your advanced Web connection query, ensuring it dynamically inserts the token.

2. Configure the Query Properly:

   • Ensure your query uses the Web.Contents function with headers properly set:

let
    Source = Web.Contents(
        "your-api-endpoint",
        [
            Headers = [
                Authorization = "Bearer " & Parameters[BearerToken]
            ]
        ]
    )
in
    Source

• Publish to Power BI Service:

  • After ensuring the query works in Power BI Desktop, publish your report.

• Set Up the Data Source Credentials in Power BI Service:In Power BI Service, go to Settings > Datasets > Data source credentials.

• • Select the authentication method as Anonymous (since the Bearer token is passed in the query itself).

• Alternative: Use a Custom Connector:

  • If this problem persists, consider creating a custom Power BI connector that supports Web V2 connections. This allows you to define the token logic and headers directly in the connector.

• Consider Using a Gateway:

  • If your API requires a specific authentication setup that cannot be handled by the Power BI Service, you can set up an On-Premises Data Gateway and configure the connection there.

Key Points:

• The Power BI Service often simplifies connections to basic Web connections, which is why advanced headers like Bearer tokens may fail.
• Using parameters or a custom connector provides a workaround for maintaining advanced Web V2 connection logic.

Please mark this as solution if it helps you. Appreciate Kudos.

[lbendlin]

ChatGPT is wrong here

Authorization = "Bearer " & Parameters[BearerToken]

Should be 

Authorization = "Bearer " & BearerToken

[FarhanJeelani]

If BearerToken is directly declared as a parameter in Power BI, we can use it without Parameters[].

But, If it's part of a custom table or query, Parameters[BearerToken] might apply.