Question

Quick Fields appends five decimals to number values it pulls from the repository

Quick Fields

Updated December 6, 2016

asked on December 5, 2016

We have a QF session that is pulling documents from the repository using LF Capture Engine for reprocessing. On the documents' template, we have two number fields. These fields contain regular integers at the time they are pulled into QF:

We have QF configured to use them:

However, when it pulls them in, this is what it displays on the processed document in the revision pane:

The format of both fields in the repository is set to "General" (the default) and there are no constraints set on them in QF. So I can't figure out where the decimals are coming from.

(This is version 9.)

0 0

Replies

replied on December 5, 2016

Inside QF, in the metadata section where you configure which template fields will be used for the document class. Do you have anything set there by chance?

Also, open the token dialog on those fields inside QF (the little arrow to the right of the token, first option) and see if you have a format set there.

0 0

replied on December 6, 2016

Can you double-check the values in the propval table?

0 0

replied on December 6, 2016 • Show version history

Well, the values in the propval table also show decimals:

This is pretty strange because the Forms Number field they are coming from is set to 0 decimal places:

The only thing I can think of is that there are formulas on these two fields that calculate the SUM from a table (e.g. =SUM(Shipment.Number_of_Packages_1)) so when Forms does the math, it leaves the decimals in there, but they aren't visible either on the Form (because of the Decimals setting above) or in the LF Client.

Of course, that doesn't explain the discrepancy in behavior between LF Client and QF. I thought they used the same metadata controls. For what it's worth, Web Access also shows the values without decimals.

In any case, regardless of whether my guess above is correct (that this is caused by the formulas), how can I fix this?

0 0

replied on December 6, 2016 • Show version history

The values as listed in the propval table are valid since the num_val column type is decimal(18,5).

I can confirm that when Quick Fields is configured for Capture Engine and in the document class, you're using the Capture Engine field tokens %(Field.[Number_field]), the processed documents in the revision pane will display the decimal point and five zeros in the field. However, this shouldn't impact storing the documents.

*Edit*

Apply field formatting in your document class. Field tokens like this should address the display issue in Quick Fields and still account for number values that do have actual decimals like 1.00001:

%(Field.Weight Shipped#"#.#####"#)

%(Field.Number of Units Shipped#"#.#####"#)

0 0

You are not allowed to follow up in this post.

Question

Question

Quick Fields appends five decimals to number values it pulls from the repository

Replies

Sign in to reply to this post.