Failure on refresh - Transient Issue, column does not exist.

[jfenico]

Hi all, I am getting a failure on refresh a couple of times a week on my report. The report, which includes data from multiple sources, one of them being Salesforce, is giving me the following error:

Failure details: The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support.

The 'Target_Group__c' column does not exist in the rowset.

The column in question is from Salesforce but is not used in any visulization. If I open the PBIX file and manually refresh, everything works fine. Any thoughts?

[QueryWhiz]

Hi @jfenico I know this reply is very late, but were you able to find a solution? In this case, as a workaround I will suggest you to try with a 3rd party connector instead of the Salesforce native connector. I've tried windsor.ai, supermetrics (which doesn't have PBI as a destination, so you first have to export to Google Sheets and then export to PBI) and funnel.io. I stayed with windsor because it is much cheaper so just to let you know other options. In case you wonder, to make the connection first search for the Salesforce connector in the data sources list:

After that, just grant access to your Salesforce account using your credentials, then on preview and destination page you will see a preview of your Salesforce fields:

There just select the fields you need. It is also compatible with custom fields and custom objects, so you'll be able to export them through windsor.  Finally, just select PBI as your data destination and finally just copy and paste the url on PBI --> Get Data --> Web --> Paste the url.

[aaronqin]

Hi @jfenico 

I recently encountered the same issue saying that one column doesn’t exist, but the dataset refreshes fine on Power BI desktop.

It turns out that the issue was to do with my Power BI desktop had auto-detect of relationship on, so there was a relationship auto created that was not intended and I wasn't aware of it. Then, one of the columns in that relationship was removed later one, this is the column that was causing issue in the refresh. After deleting the relationship and republishing the model, it refreshed fine.
Hope this helps.
Cheers

[_sfrost]

@jfenico 

Did you ever use this column in your report? if so, may be there are pinned tiles on dashboard those refer to this column? We might run into issues like this in such scenarios too.

[jfenico]

@_sfrost

Nope - I only use a few columns in the report from this table and this is not one of them.

[v-deddai1-msft]

Hi @jfenico ,

Did you modify the data structure in the data source? If so, you need to re-publish the pbix file to the Powe BI service again.

And if you have use “Pivot columns” transformation in the Power query the value of one of the columns in your data source has been transformed as the column names in your dataset. Therefore, once the value of the pivoted column in your data source changed, the column names will mismatch with the value in your data source, then the error occurs.

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Best Regards,

Dedmon Dai

[jfenico]

Hi Dedmon,

Just so I understand correctly, what do you mean by modifying the data structure? I did not use any Pivot Column transformation in the data source.

[v-deddai1-msft]

Hi @jfenico ,

Would you please check if anyone has modified  the data structure like remove columns in the data source. You need to republish it to power bi service.

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Best Regards,

Dedmon Dai