Ambiguous column name when using multiple sources

[ManchevB]

Hi Ibendin,

Thank you for pointing me in the right direction, we ended up re-writing the SQL connection and renamed the columns in the Stored Procedure so that there is no conflict. 

[lbendlin]

That's an error inside the Stored Procedure.  Fix that there.

[ManchevB]

Do you know where exactly the error could be?

The Stored Procedure done in SQL uses the same columns, with the same names I have in the other 2 sources. I tried renaming them in the Power Query editor but nothing changed.. . 🤔

[lbendlin · Accepted solution]

The error is caused by the way the stored procedure is written. Fix it in the SP.

[ManchevB]

I see, any suggestions where exactly I should check in the SP? - usually I have the SPs created for me, that's why I'm asking 

[lbendlin]

any suggestions where exactly I should check in the SP?

how would we be able to answer that without seeing the SP? It's in the SELECT statement ?