Forum Discussion

MOVC's avatar
MOVC
Resolver I
2 years ago

Dataset Refresh via API Failing

We have a dataset connected to Azure SQL published to a Premium workspace in our P1 Capacity with an incremental refresh enabled that works correctly when refreshed manually or on a schedule. However if we trigger the refresh via the API (in this case, the refresh dataset action in Power Automate) the refresh fails with the following error message:

Data source error{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Microsoft SQL: A severe error occurred on the current command. The results, if any, should be discarded.\r\nA severe error occurred on the current command. The results, if any, should be discarded."}}

 

I can't find any useful information online about this, the error message is apparently from the SQL side but that doesn't seem to make sense with it only failing for API refreshes.

Need Help

10 Replies

  • lbendlin's avatar
    lbendlin
    Super User
    2 years ago

    Which API are you using? Enhanced Refresh Request API?  Are you attempting to refresh the entire semantic model, or tables, or partitions?

     

    • MOVC's avatar
      MOVC
      Resolver I
      2 years ago

      Apologies if there was confusion, I was trying to use the Power BI connector in Power Automate (image) to carry out the refresh. There doesn't appear to be any additional settings so I assume it's trying to refresh the entire model. I can confirm that this method works for other semantic models that don't have incremental refresh enabled though, I was wondering if it was something specific about incremental refresh that was incompatible with the API method.