Preview Error

[richrich123]

Hi,

Since I upgraded to latest version, I am getting preview errors on multiple tables, was fine before. I have seen a few other people have started getting this since upgrade but none of the items suggested have resolved this. On one table (Dyanmcs (Incident Resolutions), I am only pulling 5 columns.

I need to edit my fields under 'removed columns' but can't as I am getting the error "we cannot modify this step becasue there is are error steps, please resolve those errors first

Im also getting the same problem with the systemusers table. Some others are fine.

I tried disabling this as was suggested on another post but didn't help:

Thanks

[richrich123]

@v-yiruan-msft , Im not familar with TRF as suggested in that post but either way, I cant see rolling back will help me becuase if I create a brand new PBI and just get the users or case table, it still gives this error as soon as I select the table and hit the transform button.

[v-yiruan-msft]

Hi @richrich123 ,

I found that there is one similar thread as yours, hope its solution can help you solve your problem.

Solved: Re: Preview.Error: The type of the current preview... - Microsoft Fabric Community

I updated to the latest version of Power BI, but now It's not loading at all. Refreshin just get stuck with the system users table. The steps Source and Navigation seem to be the problem, as the table does load the steps after those. But with refreshing it just gets stuck at 28 kb, while other tables load normally. 

EDIT:
Problem has been solved. I reverted back to an older version of the file (using tfs) and the issue wasn't there. The only difference is a few steps in the query that change the data type of columns. Very weird, but it works now haha  

---

If the above one can't help you, could you please provide the following info for further investigation?

1. What's the version of your Power BI Desktop? Can it work if revert back the version of your Power BI Desktop to older one?
2. Did you make any change on your pbix file?
3. What's the data source of your report?
4. The applied codes of the tables which occurred the error

Best Regards