Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago

Salesforce refresh from PowerBI.com fails

I am getting a refresh error in Powerbi.com when I try to refresh Salesforce Opportunity data.

 

Something went wrong
There was an error when processing the data in the dataset.
Please try again later or contact support. If you contact support, please provide these details.
Data source error: The 'Opportunity_Age__c' column does not exist in the rowset. Table: Opportunity.
Cluster URI: WABI-US-EAST2-redirect.analysis.windows.net
Activity ID: 11319f4a-fcef-46e6-9f3e-2b63cd874268
Request ID: 4e993b4d-52bf-de27-1457-b353d5f5bd22
Time: 2019-05-22 16:33:46Z

 

 

I can connect in desktop and refresh with out any issues.  As soon as I publish it, then try to refresh I get the above error.

 

In an attempt to troubleshoot, I built a simple one table report with just the Opportunity table.   The column is in the report

 

 

In another test, I get the same error message but with a different column.

 

Does anyone know a work around or fix?

 

Thanks

Need Help

4 Replies

  • v-frfei-msft's avatar
    v-frfei-msft
    Community Support
    7 years ago

    Hi Anonymous ,

     

    Please delete the dataset and republish the report to service to refresh it again.

     

    • Anonymous's avatar
      Anonymous
      Not applicable
      7 years ago

      Ok, I deleted the dataset, republished, ran refresh and got the same error.

       

      Something went wrong
      There was an error when processing the data in the dataset.
      Please try again later or contact support. If you contact support, please provide these details.
      Data source error: The 'Opportunity_Age__c' column does not exist in the rowset. Table: Opportunity.
      Cluster URI: WABI-US-EAST2-redirect.analysis.windows.net
      Activity ID: cdd91c17-eccf-4e56-9422-37d8c3a25624
      Request ID: 39a5add1-074f-deb1-eb29-57b059189c4a
      Time: 2019-05-23 07:00:29Z

       

      I tried it twice and got the same results.

       

      This is just a bit frustrating.  I see others having issue like this, but thier error messages are different, in that, they seem to be pointing to secruity.  This error points out a specific column.  

       

      The column gets added when I add the pull the data from SF.  

       

      I have tried removing the column in Query editor, but I still get the same error.  

  • ReportGuru's avatar
    ReportGuru
    Post Patron
    2 years ago

    Hi @Anonymous

    I know this reply is very late lol, but were you able to find a solution? I've used the Salesforce connector but I had some issues updating my data too. Maybe you can try to test your connection with a 3rd party connector. I've tried windsor.ai, supermetrics (which doesn't have PBI as a destination, so you first have to export to Google Sheets and then export to PBI) and funnel.io. I stayed with windsor because it is much cheaper so just to let you know other options. In case you wonder, to make the connection first search for the Salesforce connector in the data sources list:

     

     

    After that, just grant access to your Salesforce account using your credentials, then on preview and destination page you will see a preview of your Salesforce fields:

     

     

     

     There just select the fields you need. It is also compatible with custom fields and custom objects, so you'll be able to export them through windsor.  Finally, just select PBI as your data destination and finally just copy and paste the url on PBI --> Get Data --> Web --> Paste the url. 

     

     

     

  • metrica's avatar
    metrica
    Post Prodigy
    1 month ago

    Hi there,

     

    Since the refresh works in Desktop but fails in Power BI Service, this appears to be a schema difference between what the native Salesforce connector exposes in each environment.

     

    I would confirm that Service uses the same Salesforce account and that it has access to Opportunity_Age__c. Then create a new minimal Opportunity query with only a few required fields, disable relationship columns, set a supported Salesforce API version, and test it in Service. If the minimal query still fails only after publishing, this may require a Microsoft support case because republishing did not resolve it.

     

    Another option is Power BI Connector for Salesforce by Metrica Software: https://appexchange.salesforce.com/appxListingDetail?listingId=31526f0e-abd8-4cb5-bd1a-3bd56b5c0577

     

    It provides a prepared Salesforce source with explicitly selected objects and fields. It will not repair the existing native connector dataset automatically, but it can provide a more controlled schema.

     

    Docs:
    https://metricasoftware.com/docs/salesforce/

     

    Cheers,

    Metrica Team