Forum Discussion

Anuradha_Sinha's avatar
Anuradha_Sinha
New Member
5 years ago
Solved

Error on scheduled data refresh while no error from client for same data

Hello all,

I have created a power bi report for sharepoint list and published it to the web succesfully. Everything is fine until i refreshed the data on web using schedule refresh option, 

The error- Have tried found people having this issue but no luck to get the solution yet. If some one had same issue and solution for it, please reply. Appreciate the help as earliest.

The column 'ID' of the table wasn't found.. The exception was raised by the IDbCommand interface.

 

 

  • Hello All, 

    Thanks for replying all on this question but we finally concluded that issue was with the permissions for the account through which the data schedule to refresh, after changing that account , we didn't face this issue.

     

3 Replies

  • Hi Anuradha_Sinha 

     

    There seems to be some  reference to a column named "ID" in your data. Were you getting this error while refreshing from desktop?

    Also is it possible for you to share some data/transformation from power query to help replicate the issue

     

    Regards,

    Veena Shenolikar

    • Anuradha_Sinha's avatar
      Anuradha_Sinha
      New Member

      Hello,

      I am getting this error only on web schedule refresh not on client desktop.

      it is just a simple list of sharepoint as a data source and not much , the only think=g i noticed today is my data which loads in Power BI shows two different IDs in the list data where i don't have do in my list.

       

      Not sure if this is issue, if yes too , i have never see this yet where i have made many reports sucessfully in power BI , any idea if there is any settings of list causing this here ?

       

      Thanks for your response.

       

  • Hello All, 

    Thanks for replying all on this question but we finally concluded that issue was with the permissions for the account through which the data schedule to refresh, after changing that account , we didn't face this issue.