Forum Discussion

bo_afk's avatar
bo_afk
Post Patron
5 years ago
Solved

Column does not exist in the rowset error

Hi,

I currently have a report published to Power BI service which has been refreshing daily for the whole week. However, this morning I got an error message that the refresh failed because one of my columns "does not exist in the rowset".

I checked back my desktop version of the report and I can see that the column does exist in the data. What's odd is that the report has been refreshing fine for the whole week and I haven't published any new versions but only today I got this error message.

Does anyone know what could have caused this all of a sudden?

Thanks!

afk

Need Help
  • collinq's avatar
    collinq
    5 years ago

    HI bo_afk ,

     

    Sometimes this error is because a column was moved, renamed or removed in the original data source.  You should try to open PBI desktop, clear your cache.  Then, just to be paranoid about it.  Close Power BI and re-open it and open that file.  Then, in that file, do the Refresh and then check to see if it is there.  If it is, re-publish and see if it is now there on the Service side.  Refresh on the Service side and see if there is an error.  If there is an error still after all of that, then go backto desktop and save a renamed version of the report and publish that and see if the renamed version works.

     

    I would appreciate Kudos if my response was helpful. I would also appreciate it if you would Mark this As a Solution if it solved the problem. Thanks!
  • Anonymous's avatar
    Anonymous
    5 years ago

    HI bo_afk,

    Normally 'key value not match' issue appears when your table structure changes. AFAIK, power query will cache the first time process result data structure into the query steps. If you do any changes to your data structure(power query or database side), they not auto-sync to each step and you need to manually fix them.

    BTW, the changes you apply to desktop files not affect the published reports. If you modify the table steps, please publish the changes version to replace the published old version at the power bi service side.

    Regards,

    Xiaoxin Sheng

2 Replies

  • collinq's avatar
    collinq
    Super User
    5 years ago

    HI bo_afk ,

     

    Sometimes this error is because a column was moved, renamed or removed in the original data source.  You should try to open PBI desktop, clear your cache.  Then, just to be paranoid about it.  Close Power BI and re-open it and open that file.  Then, in that file, do the Refresh and then check to see if it is there.  If it is, re-publish and see if it is now there on the Service side.  Refresh on the Service side and see if there is an error.  If there is an error still after all of that, then go backto desktop and save a renamed version of the report and publish that and see if the renamed version works.

     

    I would appreciate Kudos if my response was helpful. I would also appreciate it if you would Mark this As a Solution if it solved the problem. Thanks!
  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    HI bo_afk,

    Normally 'key value not match' issue appears when your table structure changes. AFAIK, power query will cache the first time process result data structure into the query steps. If you do any changes to your data structure(power query or database side), they not auto-sync to each step and you need to manually fix them.

    BTW, the changes you apply to desktop files not affect the published reports. If you modify the table steps, please publish the changes version to replace the published old version at the power bi service side.

    Regards,

    Xiaoxin Sheng