Forum Discussion

bdunzweiler's avatar
bdunzweiler
Icon for Helper I rankHelper I
8 years ago
Solved

Scheduled Refresh Issue with Value.NativeQuery

We have several reports that utililze Value.NativeQuery for explicit queries that up until now had supported scheduled refresh in the Power BI Service.  We recently published a change to the report, ...
Need Help
  • bdunzweiler's avatar
    bdunzweiler
    8 years ago

    I got notification from MS Support that the issue has been fixed in the service.  I confirmed it works as the dataset now shows the refresh features (without requiring a republish) and an ondemand refresh works.

bdunzweiler's avatar
bdunzweiler
Icon for Helper I rankHelper I
8 years ago

FYI, MS identified this as a new issue as suspected.  It is on the https://powerbi.microsoft.com/en-us/support/ page

 

Some Users may fail to refresh settings after recently publishing models that use Native Query to fetch data.users may be able to avoid this issue by avoiding using Native Query during GetData, Avoid pasting Structured Query Language (SQL) queries, use stored procedures, Allow Power Query to create your query in Power BI Desktop. Engineers have found the issue and are working on a fix. Next update @ 04/11/2018 11:30 PM UTC

 

 

bdunzweiler's avatar
bdunzweiler
Icon for Helper I rankHelper I
8 years ago

I got notification from MS Support that the issue has been fixed in the service.  I confirmed it works as the dataset now shows the refresh features (without requiring a republish) and an ondemand refresh works.

  • sdjensen's avatar
    sdjensen
    Icon for Solution Sage rankSolution Sage
    8 years ago

    Hi bdunzweiler,

     

    Thank you for keeping us updated - I just made a test to see if the issues had disappeared for us as well, but that isn't the case. We don't user Value.NativeQuery in our M code, but I made a test to see if it would make a difference and voila, once I changed my query to use Value.NativeQuery and published the model I was able to schedule refresh, so that could be a possible workaround, but I really don't want to make this change at all of our customers, so still hoping that MS will fix our issue as well.