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

Question

Question

Bad field value for date field occasionally happening

Forms Administration
Updated June 5, 2015
asked on June 4, 2015

We have a perplexing problem with one of our forms.  Specifically, in a few of our submitted forms, they are unable to save to the repository, and in the Error Log it says one of the date fields is a Bad Field Value.  Looking at other Answers posts, it looks like this could be due to any of a number of things:

1) There is a mandatory field in the repository that was left blank in the form (which doesn't look to be the case for us, as no field in the repository template is mandatory).

2) The format of the field in the form does not match the format of the field in the repository (possibly the format of the date field in the form being different than what's in the repository?)

I'm trying to find any consistent issues happening across all of our forms that won't submit, but we haven't been able to identify any commonalities to this point.  However, if there's anywhere, beyond the Error Log, where I could maybe find more detailed information, I'd definitely consider this as well..

Thanks, as always, to anyone who can assist!

Marty Gaffney - Town of Okotoks

0 0

Replies

replied on June 5, 2015

Here is the error message in its entirety:

05/06/2015 5:13:44 AM
Bad field value ('AR - Rebate - Applicant Type'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Management Company'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Last Name'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - First Name'): Another operation on which this operation depends failed. [9054]
Bad field value ('Address - Primary - Complete'): Another operation on which this operation depends failed. [9054]
Bad field value ('Address - Primary - Email'): Another operation on which this operation depends failed. [9054]
Bad field value ('Address - Primary - Phone'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Utility Account Number'): Another operation on which this operation depends failed. [9054]
Bad field value ('Address - Alternative 1 - Complete'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Age of Property'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Address - Service diff than mail'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Items Purchased'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Quantity/Unit'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Hear about Program'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Program Motivate Purchase'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Amount'): Another operation on which this operation depends failed. [9054]
Bad field value ('Process - Incident ID'): Another operation on which this operation depends failed. [9054]
Bad field value ('Process - Start Date'): Another operation on which this operation depends failed. [9054]
Bad field value ('Process - Action'): Another operation on which this operation depends failed. [9054]
Bad field value ('Process - Comment'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Contact name'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Cheque Date'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Utilities Statement Date'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Planning Purchase'): Another operation on which this operation depends failed. [9054]
Bad field value ('Process - Completion Date'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Store'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Date Purchased'): Bad field value. [9017]
Bad field value ('AR - Rebate - Price'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Total'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Rebate'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Total Rebate'): Another operation on which this operation depends failed. [9054]
Bad field value ('AR - Rebate - Applied By'): Another operation on which this operation depends failed. [9054]
Message: Multistatus response. [9039]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Bad field value. [9017]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Another operation on which this operation depends failed. [9054]
Stack trace:    at Laserfiche.RepositoryAccess.EntryInfo.Save()
   at Laserfiche.Forms.CommonUtils.LFHelper.SetValueToTemplateField(EntryInfo lfDoc, String template, FieldValueCollection fvs)

The only value that actually says "Bad Field Value" is the Date Purchased, which led me to think it had to do with the formatting of the date field.  I thought that it maybe had to do with yyyy-mm-dd going to dd/mm/yyyy or something, but some of the date values in these fields have single-digit months and days, which led me to think this wasn't the issue?

Thanks again for your assistance.

Marty

 

1 0
replied on June 4, 2015 • Show version history

In the application event log, when there is an issue with a form field mapping to a Laserfiche field, all fields will report the "bad field value" error except for one specific field which may report the actual issue. Could that be the case here? Can you provide the text of the error reported in the application event log when this issue occurs?

Another possible reason for the "bad field value" error is when the value in the form field exceeds the width of the Laserfiche field it's mapped to so that's something else to check for.

Example: your Laserfiche field for "Last Name" has a width of 15 characters, but in Laserfiche Forms, someone enters "Nahasapeemapetilon" as their last name. Since the value exceeds the width of the field, it would result in an issue and all other fields from that form instance would report the "bad field value" error.

0 0
replied on June 5, 2015

So this is actually related to your other Answers post regarding the date format? You indicated that this issue only happens to some form submissions. Can you do direct comparisons of the "AR - Rebate - Date Purchased" form field in a good submission and a failed submission? Could it be an issue with MM/dd/yyyy vs dd/MM/yyyy so for example, you input a value that's 13 or larger, but it's trying to set that as the month instead of the day.

0 0
replied on June 5, 2015

I have a feeling that's what's affecting things here as well, so once I resolve the issues on the other post, I'll try re-submitting these form submissions.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...