Power BI Connector Failing - Opportunity Endpoint

Options
Jeremy Wrinkle
Jeremy Wrinkle
Name Dropper First Anniversary Facilitator 1 December 2023 Challenge: Season of Giving
in SKY Developer General Discussions

Hello:

I am getting this error message when I try to refresh a Power BI report in Fabric, while calling the Opportunity endpoint. This started around the time of the Crowdstrike debacle, so I am wondering if they are related?

  • Data source error: The '<oii>opportunity_likelihood_name</oii>' column does not exist in the rowset. Table: Opportunity.

I created a test report, with no visualizations and just the Opportunity endpoint response as a dataset. I can refresh the report in the Desktop app, but not in the service.

-JW

Tagged:

Comments

  • Alex Wong
    Alex Wong Community All-Star
    Ninth Anniversary Kudos 5 PowerUp Challenge #3 Gift Management Name Dropper

    @Jeremy Wrinkle
    did you setup a gateway?

    Power BI Connector is a custom / unofficial connector, it only exists on your desktop (or any other desktop that has the mez file installed). You need a gateway to have the power BI report refresh after it has been published to the power bi service.

    if you did have a gateway setup and refresh previously worked but failed during the global outage due to Crowdstrike, then just try refreshing on the power bi service, not on your local power bi desktop.

  • Jeremy Wrinkle
    Jeremy Wrinkle
    Name Dropper First Anniversary Facilitator 1 December 2023 Challenge: Season of Giving

    @Alex Wong

    I had my client's head of IT restart the on prem gateway server, but that hasn't worked.

  • Alex Wong
    Alex Wong Community All-Star
    Ninth Anniversary Kudos 5 PowerUp Challenge #3 Gift Management Name Dropper

    @Jeremy Wrinkle
    Try to login to the on prem gateway server, open the Power BI on PBI Desktop, and do a refresh from there, see if that works. Essesntially this is what happen when power bi service calls the gateway to run the refresh.

    May want to ensure the mez file you have on the server is the same as the one you have in your local computer

  • Jeremy Wrinkle
    Jeremy Wrinkle
    Name Dropper First Anniversary Facilitator 1 December 2023 Challenge: Season of Giving

    @Alex Wong

    The MEZ file was the issue! I had updated my copy of the MEZ file back in March, but didn't think about the Gateway. I don't understand why it didn't fail until recently, but the report refresh in the service is working now.

Categories