Forum Discussion

Simon_Furse's avatar
Simon_Furse
Copper Contributor
Feb 25, 2021

Please help with a DataSource.Error when merging two connections in power query

Hi Everyone,

I have been working with a complicated series of connections merging data from different sources (Excel sheets and salesforce reports and tables) together into the format needed for reporting. It has all been working fine so far but when I tried to do a merge on two tables (one coming from a salesforce object and the other the result of several merges) it has come up with an error message:

DataSource.Error:
Date_of_first_arrival_in_the_UK__c FROM Contact WHERE TRUE
                                                     ^
ERROR at Row:1:Column:198
unexpected token: 'TRUE'
Details:
    List

 

The strange thing is that the preview is loading all the rows exactly as I want it to, there is just an additional row added that says error in all the columns and when you click on it it comes up with the above message. It is also wierd that it mentions column 198 because I definitely don't have 198 columns in my data. The messages highlights a particular column name ('Date_of_first_arrival_in_the_UK__c') but is not specific to that column becuase when I remove that column from the table expansion it changes the error message to the next column. The error message starts to appear after expanding out the merged connection.

Can anyone explain to me why this is happening and what I might be able to do to fix the problem? Thanks very much in advance

1 Reply

  • PBIPro's avatar
    PBIPro
    Copper Contributor

    Simon_Furse 

     

    I know this is an old post, but it seems like no solution was given anywhere online and had the same issue today myself.

     

    The solution to the error came from a Boolean (true/false) data type in a previous step in the query I was merging into. I didn't have a specific need for as that data type so changed it to text and that seemed to do the trick. In all this error likely comes from power BI acting up due to a data type alignment issue in a previous step.

Resources