Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago
Solved

The name 'Table.FuzzyNestedJoin' wasn't recognized. Make sure it's spelled correctly

When I try to do a "FuzzyNestedJoin" I get this error in Data Flows:

"The name 'Table.FuzzyNestedJoin' wasn't recognized. Make sure it's spelled correctly"

 

Here is what I am doing.........

 

Table.FuzzyNestedJoin(#"Expanded Exclude", {"Account_Name"}, HPG_Roster, {"Name2"}, "HPG_Roster", JoinKind.LeftOuter, [IgnoreCase = true, IgnoreSpace = true, NumberOfMatches = 1])................

 

 

Any help would be amazing!

Need Help

9 Replies

  • PhilipTreacy's avatar
    PhilipTreacy
    Icon for Super User rankSuper User
    5 years ago

    Hi Anonymous 

    Have you got the latest version of PBI installed?

    How/where did you create that query?

    Phil

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    PhilipTreacy  I'm using Dataflows so I don't think versions apply? Thanks so much for your help. Also if it helps I the fuzzy join is between a SQL connection and an excel file. But I do the exact same steps in desktop and it works great. It seems to be something that I am doing wrong in Dataflows or a bug? 

    • PhilipTreacy's avatar
      PhilipTreacy
      Icon for Super User rankSuper User
      5 years ago

      Sorry Anonymous I was in a rush and didn't read the qs properly.

      Did you create that query by hand or by using the GUI in PBI Service?

      If you run this query is Table.FuzzyNestedJoin listed as a function?

       

      let
  Source = #shared,
  #"Converted to table" = Record.ToTable(Source),
  #"Filtered rows" = Table.SelectRows(#"Converted to table", each Text.Contains([Name], "uzzy"))
in
  #"Filtered rows"

       

      Regards

      Phil

      If I answered your question please mark my post as the solution.
      If my answer helped solve your problem, give it a kudos by clicking on the Thumbs Up.

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    PhilipTreacy If I am in advanced editor it does not show up as a function BUT when I go to click "merge queries"  at the top it gives me the option to do a fuzzy merge? THen it populates the code for me. But then I proceed to get the error. This is the same for both the query you provided and the orignial query. See the image below allowing me to do a fuzzy merge with the query you gave.

     

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    You just need to add an equals ("=") sign in front of the expression; otherwise, Power Query thinks you are referring to a table.

    ---Nate

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    Anonymous Could you please help me understand where to add the ("="). Here is the step that is failing.

     

      #"Merged queries" = Table.FuzzyNestedJoin(#"Expanded Exclude", {"Account_Name"}, HPG_Roster, {"Name2"}, "HPG_Roster", JoinKind.LeftOuter, [IgnoreCase = true, IgnoreSpace = true, NumberOfMatches = 1])
     
    Here is an example of the full advanced aditor. Notice it doesn't even give me the option to do table.FuzzyNestedJoin. It only allows for table.NestedJoin

     

     
    • PhilipTreacy's avatar
      PhilipTreacy
      Icon for Super User rankSuper User
      5 years ago

      Hi Anonymous 

      I don't think a missing = is the issue.  If you are creating the join via the GUI then it enters all the necessary syntax for you including the step name and the = before the actual transformation part.

      As the GUI offers you the option to do a fuzzy join yet does not list the fuzzy join functions as available either in the #shared query I gave you, or in the Intellisense lst in your last image, this looks like a bug to me.

      Try reporting it in Issues and see what response you get

      https://community.powerbi.com/t5/Issues/ct-p/PBI_Comm_Issues

      Phil

      If I answered your question please mark my post as the solution.
      If my answer helped solve your problem, give it a kudos by clicking on the Thumbs Up.