Question

Bad field value when entering a number into a number field

Laserfiche

Updated February 9, 2024

asked on February 6, 2024

The customer is getting the error below when trying to enter what appears to be any number into this Invoice_Number field. I tried numbers like 750 and 1 with no success, getting the same error. When I look at the fields configuration it is configured to accept numbers with no constraints. When I search the repository I see many numbers on existing documents that it appears not to accept now. What more specifically is this error stating?

Error Code: 9017
Error Message: Invoice_Amount: Bad field value. [9017]

------------ Technical Details: ------------

LFSO:
Call Stack: (Exception)
CLFFieldData::SendPropertiesToServer
ILFObjectImpl::Update
Additional Details:
HRESULT: 0xc0042339 (TestMultistatus, LFObject.cpp:710)
(LFSO/11.0.2205.11)
LFMetadata110.dll (11.0.2102.83):
Call Stack: (Current)
CLFMetadataCtrl::SaveData
Additional Details:
Exception: 0xc0042339 [9017] (Bad field value.) (CLFMetadataCtrl::SaveData at LFMetadataCtrl.cpp:1260)
Call History:
CDisplayedFieldManager::GetDisplayedFields
CPageTemplate::CheckDynamicFields
CDisplayedFieldManager::GetDisplayedFields
CFieldBrowser::ValidateFormLogicRules
CPageTemplate::RetrieveFieldValues
CDisplayedFieldManager::GetDisplayedFields
CPageTemplate::GetFieldValueAsVariant
CLFMetadataCtrl::SaveDataz

Search results of existing entries using this field

0 0

Replies

replied on February 7, 2024

Are you attempting to enter "750" or "$750"? Are you typing in the value or copying it from somewhere else?

0 0

replied on February 7, 2024

I am manually typing in numbers like 750 or 1, etc without typing a $. After I type the number and lose focus on the field, it shows a $ and the 2 decimals since it is configured as a currency field.

Here is a recording. Something else I tried was manually adding the field to a document instead of using the template it is on, in this case it works fine. Not sure why this is, the error says specifically that my Invoice_Amount value is a bad field value and I am not filling out any other fields in the template.

0 0

replied on February 8, 2024

Part of your stack trace suggests that the template might be configured with dynamic fields; is that the case, and if so is Invoice_Amount part of the relationship?

(Miruna's suggestion to open a support case is probably going to be your best bet, though)

0 0

replied on February 8, 2024

Just checked and the Dynamic Fields tab is empty.

Why is it that I see Invoice_Amount inside of a grouped collection but yet it is not a multi-value field? I thought it must be a multi-value field in order to be included in a collection?

I can not see how they added this field to the group as I can only see multi-value fields available to assign groups to

I created a support case: 236871

1 0

replied on February 8, 2024

Please open a support case and attach a briefcase with a document containing this template.

0 0

replied on February 8, 2024 • Show version history

Chad,

What you observed about the metadata pane UI showing "Invoice_Amount" as part of the multivalue field group despite the template properties in the Administration Console not showing it set that way is related.

It's unclear how the template and field got into this state, but one way to clear up this sort of corruption is to set a value for the "Group Name" in the "Field Groups" tab. Once that's done, restart the Laserfiche Server service.

When you log back into the repository and view the metadata pane for that template, you should see that "Invoice_Amount" is no longer part of the multivalue field group and you should be able to save values in that field.

Alternatively, if the intent is to have the Invoice_Amount field be multivalue and part of the same field group, then you can just go into the Administration Console and in the template properties > General tab, make that change. Apply the setting and you should be able to input and save values into that field again. No restart of the Laserfiche Server service is required in this case.

We'll do some additional testing to see if we can figure out how this issue happened in the first place.

Regards

0 0

replied on February 9, 2024

Making the field a multi-value field seems to have fixed the problem. It seems they added it to a group before removing the multi-value attribute.

1 0

You are not allowed to follow up in this post.

Question

Question

Bad field value when entering a number into a number field

Replies

Sign in to reply to this post.