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

Question

Question

Cannot store field data

asked on May 23, 2019

I am having issues with field formatting in QF. I get this error, but not with every value. I have some .NET token formatting going on, but in workflow, after this point.

 

I am unable to store these documents from Quick Fields

QFNumberError.PNG
0 0

Answer

SELECTED ANSWER
replied on May 23, 2019

How are you extracting the values?

One option might be to use formatting on the result tokens when you assign them to the fields to ensure it is a purely-numeric format.

 

%(Token#"0.00"#)

Would drop commas and always include exactly two digits after the decimal, and at least one before it,

1,000.00 ==> 1000.00

1.9 ==> 1.90

1 ==> 1.00

.99 ==> 0.99

 

Alternatively,

%(Token#"#.##"#)

Would drop commas and only include decimals and zeros when necessary,

1,000.00 ==> 1000

1.90 ==> 1.9

1.00 ==> 1

0.99 ==> .99

 

You'll need to adjust it if you can have more than two decimal places because otherwise 1.999 would become 2.00

If you're putting this into a number metadata field, the formatting shouldn't really matter as long as it is numeric and you don't lose any accuracy.

1 0

Replies

replied on May 23, 2019

Have you noticed any difference between the values that work and the ones that don't? For example, does it only affect values over 999.99 where the , comes into play?

1 0
replied on May 23, 2019

yes, it does

0 0
SELECTED ANSWER
replied on May 23, 2019

How are you extracting the values?

One option might be to use formatting on the result tokens when you assign them to the fields to ensure it is a purely-numeric format.

 

%(Token#"0.00"#)

Would drop commas and always include exactly two digits after the decimal, and at least one before it,

1,000.00 ==> 1000.00

1.9 ==> 1.90

1 ==> 1.00

.99 ==> 0.99

 

Alternatively,

%(Token#"#.##"#)

Would drop commas and only include decimals and zeros when necessary,

1,000.00 ==> 1000

1.90 ==> 1.9

1.00 ==> 1

0.99 ==> .99

 

You'll need to adjust it if you can have more than two decimal places because otherwise 1.999 would become 2.00

If you're putting this into a number metadata field, the formatting shouldn't really matter as long as it is numeric and you don't lose any accuracy.

1 0
replied on May 24, 2019

Thanks!!

0 0
replied on May 24, 2019

I applied the formatting to a field, but it does not transfer through to the scanned results

Formatting.PNG
Formatting.PNG (1.09 KB)
0 0
replied on May 24, 2019

When you say it doesn't transfer through to the scanned results, what do you mean?

If you look at the output logs, it should show you what value it had for the source token. Copy one of the problem values from there and in the Token Editor use it to test the token formatting.

0 0
replied on May 24, 2019 Show version history

I get a value like 194 81

I need to format it to be 194.81

 

Where is token editor? I have yet to play with that EDIT: found it

0 0
replied on May 24, 2019

Is there a way to insert the decimal if it isn't grabbed by ocr, or is non-existent

0 0
replied on May 24, 2019

In the spot where you set the field value, right click the value and "Token Editor" is at the bottom. Or click the > next to the field and it will be at the top.

I wouldn't add the , to the formatting rule. If your metadata field is numeric, then it won't matter anyway and it could just cause issues.

To deal with the missing decimal, you could trying the following:

  1. Function - Trim, to remove any leading/trailing spaces.
  2. Function - Split, on the blank space
  3. Apply Index - All values separated by .
  4. Apply Formatting

This can all be done in the token editor, and the order of the functions is important. It would look something like this

%(Token#@Trim;Split( )@##[.]##"0.00"#)

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

Sign in to reply to this post.