LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Fitzy

Hi Folks,

I am struggling with the exact tab configuration when using the "Fuzzy X-ref" node.

I am trying to get the Exact tab working first, before I worry about the configuration in the Fuzzy tab.

I am trying to exact match on two fields:
Left input:
'Issue_Type','Changed_By_User_Id'
Right input:
'Source_Issue_Type_CODE','User_Id'

This will only bring back matches for "Issue_Type" and "Source_Issue_Type_CODE"

If I switch the order around to:
Left input:
'Changed_By_User_Id','Issue_Type'
Right input:
'User_Id',''Source_Issue_Type_CODE'

This will only bring back matches for "Changed_By_User_Id" and "User_Id".

Anybody can inform me why it behaves this way ?

Kind regards,
Sean

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: ltolleson

There are some technical reasons of which I am uncertain, but I do know that using multiple key values in the Fuzzy nodes do not work exactly the same as the standard Join/X-Ref nodes.

When you use the standard Join/X-Ref it is acceptable to use a comma separated list of key values and the node automatically concatenates the values and treats those as one key value.

Unfortunately when the Fuzzy nodes were designed they were not built to follow this same form. To allow multiple key values in the Fuzzy nodes it is required to concatenate the values together as one value. You can do this by simply using the strCat(field1, value2, etc....) as the key. You can also use the + operator as well. Example... field1 + value2 + etc...

The Fuzzy nodes do not parse and interpret a comma separated list of key values, you must build the key.

I know that is confusing if you have not used it before.

Hope this helps.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: ryeh

This is the second time this has come up in the past few days. Also see:
http://community.lavastorm.com/threa...th-Fuzzy-nodes

I've checked with development. Right now it's only matching on the first key. A request has been made to extend the match to multiple keys.