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

Question

Question

LF Forms Error Invalid number of rows in collection/table

asked on April 12, 2018

I have a form that has multiple tables of one row each where users check boxes and attach documents.  The form was working properly, but I had to add several more tables for some additional forms now required in the process, and now am getting the following error message:

Field Name:, Position: 113, Error: Invalid number of rows in collection/table. [LFF9313-InvalidNumberOfElementsinCollection] [LFF9312-ErrorOccuredDuringFormsValidation]

I'm not quite sure where to start with troubleshooting this.  I have no javascript, only css to hide each of the table names.  We are running Laserfiche Forms Professional Version 10.2.1.246

Thanks for any help.

0 0

Answer

SELECTED ANSWER
replied on April 17, 2018

Yes, I did have lookup rules, and the error was on the message start event when the very first form was submitted.  After consulting with my VAR, he had me install the latest patch for Forms and it corrected the issue.

1 0

Replies

replied on January 2, 2019

This seems to have returned in 10.3.1. We want to do a lookup of essential functions, and have the user enter a result, into the second column, for each essential function. We do not want them to add rows to the table though. So we set it up with a 0-min to 0-max for appending rows, which removes the add button.

When the user selected to save a draft, they received this message that the table contained an invalid number of rows and they were taken away from their submission with no draft saved. We could not recover the data.

Can the error be opened in a new tab, alert, or consoled instead? Only in the last 6 months or so have I been running into many many forms errors that take the user away from their current location in the browser without opening a new tab and lose all the data entered.

1 0
replied on April 15, 2018

Hi Melanie,

1. Is there any lookup rule in your table? We have some known issues causing this validation error with lookup filling the table on certain conditions.

2. At which step did you get the error, message start event or user task? If it's on user task, maybe your previously submitted data do not meet the setting of newly added tables.

0 0
SELECTED ANSWER
replied on April 17, 2018

Yes, I did have lookup rules, and the error was on the message start event when the very first form was submitted.  After consulting with my VAR, he had me install the latest patch for Forms and it corrected the issue.

1 0
replied on May 15, 2018

I can't find the individual file for this.   Is this only attached within the Avante or Rio full downloads?  Or can you provide the link to the patch that you installed that fixed this?

I am currently experiencing the same issue where the lookup is correct and I am receiving this error.

Also:

Is there a way to identify exactly which Row in the table is causing the error from the Position 30?

I'm not sure how to step through where the Position is referenced.

Thanks!

1 0
replied on August 20, 2019

Similar to Chad, I am seeing this in 10.3.1.

My scenario is that the table is doing a lookup from a table for prior disciplinary actions.  On initial completion of the form, it fills in the table if 'Prior Occurrences' is checked.  (All fields filled in from lookup are set to READ ONLY.)  Once the form is submitted, the business process runs a workflow to take the Current Discipline and add it to that table.

HR review is the next step after the workflow updates the Prior Occurrences SQL table.  HR can submit the form to go back for more information or to go on for processing.  When the form is passed back for more information and the supervisor fills in the comments and submits the form, the following error occurs:

 

Errors encountered during forms submission: <br>Field Name: Occurrence Date, Position: 24, Error: Invalid number of rows in collection/table. [LFF9313-InvalidNumberOfElementsInCollection] [LFF9312-ErrorOccuredDuringFormsValidation]<br>Field Name: Action Taken, Position: 26, Error: Invalid number of rows in collection/table. [LFF9313-InvalidNumberOfElementsInCollection] [LFF9312-ErrorOccuredDuringFormsValidation]<br>Field Name: Violation, Position: 25, Error: Invalid number of rows in collection/table. [LFF9313-InvalidNumberOfElementsInCollection] [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: 8/20/2019 10:05:58 AM (Eastern Standard Time)
HTTP Status Code: 400
Business Process ID: 84
User: WENGER\MichelleS
IP: 192.168.1.179
Browser: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko
Instance ID: 8687
Business Process Name: HR - Team Member Disciplinary Action

Stack Trace:
Caught exception: Laserfiche.Forms.CommonUtils.Exceptions.LFFormsException
Message: Errors encountered during forms submission: <br>Field Name: Occurrence Date, Position: 24, Error: Invalid number of rows in collection/table. [LFF9313-InvalidNumberOfElementsInCollection] [LFF9312-ErrorOccuredDuringFormsValidation]<br>Field Name: Action Taken, Position: 26, Error: Invalid number of rows in collection/table. [LFF9313-InvalidNumberOfElementsInCollection] [LFF9312-ErrorOccuredDuringFormsValidation]<br>Field Name: Violation, Position: 25, Error: Invalid number of rows in collection/table. [LFF9313-InvalidNumberOfElementsInCollection] [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 August 22, 2019

Edits:  Turned off backend validation on the initial form (used in message start, HR review, and supervisor update tasks).

Disabled the prior discipline table lookup rule in the next three forms: Supvr/TM, HR sign, Mgmt sign

Error stopped occurring.  What is impact of NOT using the backend validation on my message start form?

1 0
replied on August 22, 2019

I always turn off backend validation, otherwise I get these errors and no backup of the submission.

So far there has been no impact of turning it off, but on our forms, if we need to verify any input data we use either javascript or conditions on the field and notify the user with inline messages as to what they did wrong.

2 0
replied on August 22, 2019

Chad, that's good to know.  I'm not very conversant in javascript, but using field constraints should capture most of what we'd be concerned with for now.  Thanks.

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

Sign in to reply to this post.