There was an error when processing the data in the dataset.

[yvonneT]

I am receiving this error on a field even through I have not made any changes to anything in this table.  The automatic refresh I have was disabled so I need to figure out how to fix the issue so it can start refreshing properly again.  Please advise.

[v-sgandrathi]

Hi @yvonneT,

Thank you @pborah for your insights on this issue.

 I'm glad that your query was resolved. If the response provided by the community member addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.

Thank you for your understanding!

[v-sgandrathi]

Hi @yvonneT,

We haven’t heard from you on the last response and was just checking back to see if your query was answered.
Otherwise, will respond back with the more details and we will try to help .

Thanks for using Microsoft Fabric Community Forum.

[v-sgandrathi]

Hi @yvonneT,

As we did not get a response, may I know if the above reply could clarify your issue, or could you please help confirm if we may help you with anything else?

And if the provided information meets your requirements, you can Accept the solution and also give Kudos on that reply. It helps other users who are searching for this same information and find the information.

Your understanding and patience will be appreciated.

Thank You.

[yvonneT]

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]

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.

[yvonneT]

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.

[yvonneT · Accepted solution]

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.

[pborah]

@yvonneT that's great to know that a simple refresh resolved your issue, in which case I'm thinking the refresh simply updated your columns automatically.

For future's sake however, for a very similar error message (column doesn't exist in rowset), sometimes the solution is more complicated if you have calculated columns at the data transform stage that depends on a preexisting column coming in from your source. In that case a refresh will fail and you might have to rectify the calculated columns first.

Refreshes also fail if suddenly in your data model, a table on one side of a 1-to-many relationship has duplicate keys. The error usually happens at source i.e. a human entering duplicates in a form. In SQL it might not matter because the table might not be related to another table. But in Power BI if it's part of a relationship to make your report work, the duplicate keys will fail the refresh.

In my experience these two are the most common causes for refreshes failing in service. The error message details provide decent clues.

Please give me kudo if I was able to help you with the solution, I'd appreciate it! All the best!

[yvonneT]

I don't know exactly because everything was the same before and after, no column changes.  I am glad that the refresh resolved the issue though.  I do appreciate your prompt responses and help! Thank you so much!

[pborah]

What are the details of the refresh error? It should say more in the message.