You are viewing limited content. For full access, please sign in.

Question

Question

Multi Value Pattern Match Edit

asked on November 4, 2016 Show version history

I am OCRing a List of invoice #s, unfortunately some 0s are read as Os:

 

I have a Multi value Pattern Match in my workflow to identify the # I wish to grab (note not all the values I am pattern matching fit the above format, for example I am also retrieving C043008 & 74624, but there is no issue with these)

I am attempting to correct the OCR misread via token values in my workflow.

In the for Each Value I am using the PMed Inv #s

the conditional sequence checks if the current value matches expression INVO\d{6}

the Assign Token Values 2 Modifies the current value to INV0%(ForEachValue2_Current Value#<\d{6}>#)

The Assign Field Value Assigns the current value, and appends to the existing values

When I run this workflow I return:

 

The there are 48 inv #s on the example invoice I am using, in my fields I get INV0049216 45 times and none of the numbers after that appear.

I am missing something/doing something wrong, but I cannot seem to find what that is.  

How can I single out those PMed values, replace with the corrected info and assign those values to a metadata field?

 

Darren

 

 

 

 

 

0 0

Answer

SELECTED ANSWER
replied on November 4, 2016

If the condition in your sequence is not satisfied, then Assign Token Values does not run. So the token it would generate still has the value from the previous iteration of the For Each Value loop. So once you set the token to INV0094216, the next 44 times, it just runs with that value because it never goes into the Conditional Sequence again. This is a guess since you're not showing the condition in your screenshots.

You need a Conditional Decision where if you have INVO, you correct the token and set the field value AND in a second branch, you just set the field directly for the case where you have INV0.

1 0
replied on November 4, 2016

That did it! Thanks, for some reason I was not seeing that today on my own

0 0
replied on November 4, 2016

No problem. We've all been there wink

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.