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

Question

Question

10.3.1 - Back end validation requiring field values even though it's turned off

asked on April 24, 2018 Show version history

We upgraded from 10.3 to 10.3.1 last night in the hopes it would fix some of the major issues we're having with 10.3. After the upgrade, we're now experiencing new issues, one of which is that hidden fields set to ignore data when hidden are requiring that values are entered even when they're hidden. Backend validation is turned off for the form. The form wasn't requiring values in those fields before this upgrade. Why now?

Is anyone else having this issue?

0 0

Replies

replied on April 24, 2018

Hi Sheila,

Can you give more details on the issue:

Did you set the fields hidden by field rules? If so, what is the field rule setting?

Do you have any custom JavaScript on the form? Is there any frontend js error when filling and submitting form? You can check it with Chrome developer tools.

And what is the detailed error in the validation?

0 0
replied on April 25, 2018

Hi Shiela, I had noticed this as well when I had set Fields to Hide but had chosen the Save the Data feature. Rui, this the error as the Event viewer logged it.

+ System 

  - Provider 

   [ Name]  Laserfiche-Forms-App 
   [ Guid]  {98141CA4-660B-51C6-66B4-EC37F5B2FD87} 
 
   EventID 9320 
 
   Version 0 
 
   Level 2 
 
   Task 56214 
 
   Opcode 0 
 
   Keywords 0x8000f00000000000 
 
  - TimeCreated 

   [ SystemTime]  2018-04-20T20:20:39.085844600Z 
 
   EventRecordID 3786 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  16212 
   [ ThreadID]  14880 
 
   Channel Laserfiche-Forms-App/Operational 
 
   Computer LaserVM 
 
  - Security 

   [ UserID]  S-1-5-21-3608839966-4280778587-1954409852-1000 
 

- EventData 

  message Errors encountered during forms submission: <br>Field Name: Customer, Position: 13, Error: This value is required. [LFF9300-ValueRequired] [LFF9312-ErrorOccuredDuringFormsValidation]<br>Field Name: Customer, Position: 13, Error: This value is required. [LFF9300-ValueRequired] [LFF9312-ErrorOccuredDuringFormsValidation]<br>Field Name: Customer, Position: 13, Error: This value is required. [LFF9300-ValueRequired] [LFF9312-ErrorOccuredDuringFormsValidation]<br>Field Name: Customer, Position: 13, Error: This value is required. [LFF9300-ValueRequired] [LFF9312-ErrorOccuredDuringFormsValidation]<br> You can click the back button on the browser to correct and resubmit the form. [LFF9320-FormsValidationAggregateException] Details: URL: /Forms/Form/Submit?source=formiframe Error: FormsValidationAggregateException Date: 4/20/2018 4:20:39 PM (Eastern Standard Time) HTTP Status Code: 400 Business Process ID: 86 User: Forms IP: ::1 Browser: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Instance ID: 1384 Business Process Name: BrokerageDocIngestor Stack Trace: Caught exception: Laserfiche.Forms.CommonUtils.Exceptions.LFFormsException Message: Errors encountered during forms submission: <br>Field Name: Customer, Position: 13, Error: This value is required. [LFF9300-ValueRequired] [LFF9312-ErrorOccuredDuringFormsValidation]<br>Field Name: Customer, Position: 13, Error: This value is required. [LFF9300-ValueRequired] [LFF9312-ErrorOccuredDuringFormsValidation]<br>Field Name: Customer, Position: 13, Error: This value is required. [LFF9300-ValueRequired] [LFF9312-ErrorOccuredDuringFormsValidation]<br>Field Name: Customer, Position: 13, Error: This value is required. [LFF9300-ValueRequired] [LFF9312-ErrorOccuredDuringFormsValidation]<br> You can click the back button on the browser to correct and resubmit the form. [LFF9320-FormsValidationAggregateException] at E_Forms.Controllers.FormController.Submit(FormCollection collection) at lambda_method(Closure , ControllerBase , Object[] ) at System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters) at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters) at System.Web.Mvc.Async.AsyncControllerActionInvoker.<BeginInvokeSynchronousActionMethod>b__39(IAsyncResult asyncResult, ActionInvocation innerInvokeState) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`2.CallEndDelegate(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3d() at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass46.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f() at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass46.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f() at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass21.<>c__DisplayClass2b.<BeginInvokeAction>b__1c() at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass21.<BeginInvokeAction>b__1e(IAsyncResult asyncResult)  
 

0 0
replied on April 25, 2018

Hi Steve,

Your issue is different from Sheila's. You have field rule configured to "save the data", so you must have the hidden required field filled with value, otherwise it would show LFF9300-ValueRequired error from backend validation, just like what you have seen.

0 0
replied on April 25, 2018 Show version history

I'm hiding a section with field rules. Backend validation is turned off and the rules say to ignore data when hidden. Yet I still get the message. I found last night that it was because of a calculation field in a table row. When the section is hidden, the calculation field requires that values be entered in 2 other fields in the row. When the section is displayed, the two fields are required fields, so values have to be entered. I had to add 0 as a default value to those fields to get this to work. Not what I want to do because it's extra mouse-clicks for submitters, but I tried several other formulas and they don't seem to recognize that a row exists and so cause a failure too.

The message displayed is:

'' cannot be used as a numeric value. [LFF1012-InvalidNumericValue]

I have js and css on the form, but I tried removing both to see if that was the issue. The form still wouldn't submit. However, there is an error in the console log: "Uncaught SyntaxError: Invalid or unexpected token   Submit: 66" When I click on that, it displays code that isn't mine:

0 0
replied on April 25, 2018

We have got a support case with the error. Actually this is not error from backend validation so turning off backend validation has no effect here.

This will be fixed in the coming 10.3.1 Update 1. Sorry for the inconvenience.

 

0 0
replied on April 26, 2018

Thanks for letting us know. When is Update 1 expected to be released, and what other fixes do you think it will include?

Any heads up would be appreciated because we've been fighting the 10.3/10.3.1 releases for the last 4 weeks, creating workarounds for showstopping issues like Workflow Service Tasks that never return, monitoring everything going through the system, re-routing forms that end up in the wrong user tasks for some reason, modifying virtually every field on each form and saving it back to its original configuration so the database would recognize all the settings, ...

We've spent a lot of time after the upgrade trying to keep our mission-critical processes alive and viable. I'm sure we're not the only customer in this boat!

 

0 0
replied on April 26, 2018

There is no exact ETA for Update 1 because we are still trying to fix issues as much as possible. All the fixes for issues reported from Answers and support cases on 10.3.1 would be included in this hotfix, including fixes on high memory usage and a few bugs on fill form.

If you got anything that might be a bug, please let us know.

0 0
replied on May 23, 2018

The issue that calculations in tables are not getting ignored when the table is hidden, ignore data and fields are read-only has been fixed at Forms 10.3.1 Update 1, and you can download patch file at https://support.laserfiche.com/kb/1013963/list-of-changes-for-laserfiche-forms-10-3-1-update-1

0 0
replied on May 24, 2018

Thanks!

0 0
replied on May 15, 2019

I'm not sure if this is the exact same issue, but I just encountered something like this on a client system running version 10.2.1. A number field gets its value from a calculation between two required table fields. When the section containing the number field and table are hidden, the form throws an error when you try to submit.

It turns out that this was from "divide by zero" errors. One part of the formula was averaging the values of a column in the table, which divides by zero when the table is hidden/blank. Another part is dividing by a sum, but when the table is blank that sum is 0 and also causes the error.

 

I resolved this by using the following syntaxes:

 

AVERAGE(Table.Column1) IFERROR(AVERAGE(Table.Column1),0)

Using the "IFERROR" syntax means that if there is a divide by zero here, it will just return 0.

/ SUM(Table.Column1) / MAX(1,SUM(Table.Column1))

Using the "MAX" syntax means that if the table is blank or hidden, the MAX will return 1.

 

I hope this is helpful to someone.

replied on December 6, 2019

Still waiting on a fix for this, in 10.4

0 0
replied on December 8, 2019

Hi Chad, the issue reported in this Answers post was included in 10.4.0 release. As far as we know there was no remaining issue on this post.

Can you describe the issue you met?

0 0
replied on December 9, 2019

I turned off Validation, but still received the error [LFF1012-InvalidNumericValue] upon submission. The switch to turn off Validation is not working.

1 0
replied on December 10, 2019

The error [LFF1012-InvalidNumericValue] is from backend formula calculation, not backend validation. So turning off validation has nothing to do with this error.

Can you try to find out which formula is causing the error?

0 0
replied on December 11, 2019

Finally discovered a calculation had been entered into a number field =somevar/somevar and I needed to wrap it in a round function to match the number fields rule for maximum decimals.

Javascript is so much safer because it doesn't cause any problems if the output doesn't match a field's rules and if you want to make sure the rules run on your input we just use .change()

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

Sign in to reply to this post.