Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago
Solved

Service Report stops returning data

Hi We have a Sevice report. This is working fine,  then stops returning any data. The report refreshes without error but returns no data.   The fix is to download the report to desktop, refresh th...
Need Help
  • Anonymous's avatar
    Anonymous
    7 years ago

    Finally I think this has been solved. This is a direct query report, so the filter below requires a download and refresh 

     

    #"Filtered Rows" = Table.SelectRows(#"Sorted Rows", each Date.IsInCurrentMonth([Date])) 

     

    The solution is to change the logic so the query is passed through to the database

     

    #"Filtered Rows" = Table.SelectRows(#"Sorted Rows", each ([ThisMonthFlag] = "Y"))

     

    This makes sense now. but I am not sure if this behaviour is by design ?

Anonymous's avatar
Anonymous
Not applicable
8 years ago

HI Anonymous,

 

Did you use azure sql datasource?

 

If this is a case, current it seems like a known issue on azure datasource, I think your scenario may due to engineers fix operations.

 

Reference:

Power bi Support

Users may not be able to set credentials if they are using OAuth2 for SQL Azure or AS Azure data sources. Engineers are aware of the issue and are working on a fix . Next Update @06/08/2018 14:30 PST

 

Regards,
Xiaoxin Sheng

  • Anonymous's avatar
    Anonymous
    Not applicable
    8 years ago

    Thanks Xiaozin,

     

    Yes it is a Azure SQL Datasource. Would the fix you suggested apply when using an SQL account?

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      Hi Anonymous,

       

      This issue seems closed on support page, did this works on your side?

       

      Regards,
      Xiaoxin Sheneg

      • Anonymous's avatar
        Anonymous
        Not applicable
        8 years ago

        Hi,

         

        It has just happened again. Report is working fine then stops returning data. I download the dataset, renenter the SQL creadentials and publish. All is well again.

         

        One observation I could make is that (on this accasion) the report is using a mixture of dbo tables and another schema. On this report I noticed that the dbo schema was returning data and not the other schema. Maybe this is a known issue ?

         

        Thanks