Forum Discussion
There was an error when processing the data in the dataset.
Well after hours of trying to figure out what the issue was all I had to do was log in to powerbi desktop and refresh the dataset then went into powerbi online and refreshed and it was successful so i turned back on the refresh schedule.
This is what is in the details:
Data source error: The '<oii>Solicitation Number</oii>' column does not exist in the rowset. Table: table.
Cluster URI: WABI-WEST-US-E-PRIMARY-redirect.analysis.windows.net
Activity ID: a4c20721-3b24-4563-9bdc-cade099f199c
Request ID: 386c04f5-c5c7-2a5d-ffcb-25bdf88a3151
Time: 2025-02-27 16:52:00Z
I have not changes to the Solicitation Number field, it has been on this table from the start.
- pborah
Solution Sage
Thanks yvonneT . Please check the pbix or pbir file. Something has changed in your underlying data messing up your transformation steps in "Transform Data". Compare your dataset between the source (SQL, Excel, etc.) and the pbix/pbir file. Additionally check the various transformation steps in the data editor in Power BI. Your dataset could be erroring out at one of those steps causing the subsequent transformations to fail.
All of these things will cause your refresh to fail.
Hope this helps.
Ok, I will do that now and see what I find. It is just frustrating as I am the only one that has access to made changes and I haven't made any changes to this in months. Can this only be done through desktop Powerbi? or can this be done with the online version?
Thank you!
- pborah
yvonneT you'll have to do this in desktop. You cannot do this online. The changes haven't happened in your report, they have occurred in the source (SQL, or excel file or whatever it is). Someone made changes to the source tables and did not inform you. You will have to edit your data transform to reflect those changes properly in your report. PowerBI is expecting the data to come in a certain way and your source is sending the data a different way now. That's where the disconnect is.
And no problem! This happens all the time when the analyst doesn't have direct control over the data source.
