Join SQL Query + CSV doesnt work

[ivamuno]

Hi,

I am having the following problem and I dont know why it is failing... I dont know if it is a bug or it is because of permissions/privacy.

 I merge two queries, one from CSV and another one from SQL query, like this:

And the merge (left join) is done correctly as you can see below (it is Power Query Editor):

Then, I try to show the data in any chart but column is always blank (it is Power BI Desktop (March 2018)). See data view:

Do you know why?

P.S. For now "Private Levels: Always ignore."

Thanks in advance.

[Greg_Deckler]

That's a very difficult problem to troubleshoot in a forum. Perhaps you could paste your query code from Advanced Editor?

[ivamuno]

Hi,

Sorry, I am very new in PowerBI, is it what you need?

let

   Source = Table.NestedJoin(SlowTrxsByDate,{"ProcessedTransactionGuid"},HSMSlow,{"TraceCorrelationKey"},"HSMSlow",JoinKind.LeftOuter),

   #"Expanded HSMSlow" = Table.ExpandTableColumn(Source, "HSMSlow", {"HSMTime"}, {"HSMSlow.HSMTime"})

in

   #"Expanded HSMSlow"

P.S. If I join two excels it works.

Thanks!

[Greg_Deckler]

OK, that's very strange. On the odd chance that @ImkeF has seen something like this I will tag her but this really seems like something that you should post to the Issues forum here:

https://community.powerbi.com/t5/Issues/idb-p/Issues

Or if you have a Pro account...I would submit this as a support issue. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".

[ivamuno · Accepted solution]

Hi,

I found the error! It is because string comparision.

I dont know why PowerBI Editor applied lower case function to GUID to the first query. If you see the two first pictures the GUIDs are in lower case but in the third picture (PowerBI Desktop) it is in upper case.

I realized because PowerBI Editor start working well, it returned GUID in upper case for SQL query and lower case for excel query.

P.S. PowerBI needs GUID data type, XP. 

Thank guys for helping!

[ImkeF]

That looks like a bug to me as well (just be aware that the sort order might have changed. So if there are empty values in it, the values you're looking for might be further down).