Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.
SOLVED

Fuzzy match tool - field conversion error limit reached

knozawa
11 - Bolide

Hello,

 

I am using a fuzzy match tool and got an error message:

Field Conversion Error Limit Reached.

Fuzzy match_field conversion error limit reached.png

When I checked the size of the field, it was 1073741823.

 

I also obtained 20 conversion errors like this:

fuzzy match_conversion error.png

 

Does anyone know how to solve this issue?

 

 

Sincerely,

Kazumi

 

 

4 REPLIES 4
Inactive User
Not applicable

Are you using a default match style that is character or number specific, such as zip code? I would also try stripping/replacing any special characters off as it appears to not like some Unicode characters (try basic number or character processing).

knozawa
11 - Bolide

@Inactive User,

 

Thank you for your suggestions. 

 

I am using the default Name match for the fuzzy match tool.

Before the fuzzy match tool, I used the formula:

DecomposeUnicodeForMatch([Concat_Name])

to standardize the Name field.

 

However, it appears that some unicode characters were not convertible using the formula.

 

I'm wondering if there are any other way to standardize the name field. 

 

Sincerely,

Kazumi

jm_idm
7 - Meteor

I have a process that is giving the same error about the Unicode characters.  However during our file prep process, we use the following regex_replace in a multi-tool to remove unicode.  Is there additional code we need to add to this? 

 

regex_replace([_CurrentField_],'[^\x00-\x7f]', '')

knozawa
11 - Bolide

Thank you @jm_idm

 

This formula removed unicode characters and disappeared conversion errors in fuzzy matching tool.

 

Sincerely,

Kazumi

Labels