Forum Discussion
Helper IColumn does not exist in the rowset, Desktop only
I started to get this error in one of my models a month ago " ......column does not exist in the rowset" but it does. I thought I had done something wrong and have not had the time to problem solve it. I found it strange as the columns are there and I have not changed anything. It fails on deskop Powerbi however this model refreshes via the access point without giving this error at all.
The today it happens in a different model hence why I googled the error and found this post. Has their been any resolution on this? Now that I think of it this happend after I updated power bi desktop (bit over a month aog). I currently have Mar 2020 version.
amyWMFSHi CandiceSonnekus,
I've had a number of Teams screen share sessions with people from Power BI, so far we've identified that it had to do with the header for the columns that produce that error: they all have a "line feed" line break (when you do Alt + Enter within an excel cell). Some of my colleagues with the same version of power bi and excel as me did not have that problem though, which is odd.
Unfortunately due to recent workload i've had to defer any further sessions with them, but we'll be picking it up in a couple of weeks or so, so maybe we'll find a solution then.
Amy
Hello amyWMFS
Thank you for the reply. I currently have version 2.79.5768.921 and see there is a new version released 1 April 2020 2.79.5768.1082 which I am installed and still same error.
Hear you regarding the "line feed" on Alt + Enter however this was working before I updated with the latest Power Bi version (92.79.5768.921). The strange part also is that it works in fresh mode via the access point without giving this error at all?
So when I want to make changes to my dashboard via the deskop and upload for these changes I can't as it keeps throwing this error. It is with 2 of my models now however have not had to much updates on my existing models of late until now, so maybe more. So I am stuck with this bug and have searched the web and as of yet no resolution. Unless its a bug that only Microsoft can fix?
- amyWMFS
yes, same here, it was working fine until I upgraded to the March version.
As we don't know exactly what's gone wrong, I can't really say whether it's something only MS can fix, but it does seem like it. So far they seem stumped by this error.