Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
4 years ago

Refresh starts over

Hi all,   I have a query (or a few) that was getting progressively slower and now often fails due to timing out.   I noticed in the Desktop application that the refresh of certain of the bigger q...
Need Help
Anonymous's avatar
Anonymous
Not applicable
4 years ago

Renaming the column becomes necessary when using Table.Join (as opposed to Table.NestedJoin) because you can't have two columns with the same name, which will happen after the join (unless you use JoinKind.Inner.

 

--Nate

  • Anonymous's avatar
    Anonymous
    Not applicable
    4 years ago

    Hello,

     

    I tried to implement your solution. To begin with, History would now be stuck for ours on "Evaluating" as the only query.

     

     

    It seems to take ~5 minutes in DAX Studio - but goes on forever in PowerBI Desktop.

     


    This is my new query

    let
    Source = Table.Join(CostDownAnalysis,{"IdeaIdCDA"},#"Idea Table",{"IdeaID"},JoinKind.LeftOuter)
in
    Source