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

Discussion

Discussion

Forms - How can my field values be bad if the restrictions are determined by the form

Updated January 23, 2015
posted on January 23, 2015

Every single field in my form is reporting a bad value in the event viewer and the form is not being submitted. How as the user can I be entering bad values into all my fields if the restrictions are set in the form itself. Some of these fields are even defaulted with a value to start.

 

1/23/2015 6:19:34 PM
Bad field value ('UCI#'): One or more required fields were omitted. [9066]
Bad field value ('Vendor Name'): One or more required fields were omitted. [9066]
Bad field value ('Vendor#'): One or more required fields were omitted. [9066]
Bad field value ('Vendor Phone'): One or more required fields were omitted. [9066]
Bad field value ('Location of Service'): One or more required fields were omitted. [9066]
Bad field value ('Name and Cred'): One or more required fields were omitted. [9066]
Bad field value ('Description of Services'): One or more required fields were omitted. [9066]
Bad field value ('Service Code'): One or more required fields were omitted. [9066]
Bad field value ('Start Time'): One or more required fields were omitted. [9066]
Bad field value ('End Time'): One or more required fields were omitted. [9066]
Bad field value ('Name of Parent'): One or more required fields were omitted. [9066]
Bad field value ('Funding Agent'): One or more required fields were omitted. [9066]
Bad field value ('Date of Service'): One or more required fields were omitted. [9066]
Bad field value ('Location'): One or more required fields were omitted. [9066]
Bad field value ('SigImage'): One or more required fields were omitted. [9066]
Bad field value ('SigImage2'): One or more required fields were omitted. [9066]
Bad field value ('EmployeeID'): One or more required fields were omitted. [9066]
Bad field value ('ClientID'): One or more required fields were omitted. [9066]
Bad field value ('Supervisor'): One or more required fields were omitted. [9066]
Message: Multistatus response. [9039]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
One or more required fields were omitted. [9066]
Stack trace:    at Laserfiche.RepositoryAccess.EntryInfo.Save()
   at Laserfiche.Forms.CommonUtils.LFHelper.SetValueToTemplateField(EntryInfo lfDoc, String template, FieldValueCollection fvs)

 

0 0
replied on January 23, 2015 • Show version history

When you see a message like that, it doesn't necessarily mean that every form field that you have mapped to a Laserfiche field was omitted. Usually it's just one of the fields, but I agree that the above message isn't as useful because it doesn't specifically point out which is the problem field. Perhaps you can go back and look at the submission results for that business process to find the form that's suspended and then review each of the form field values for that submission to confirm if every single one has a value.

Maybe if you know that not all of the Laserfiche fields listed in that message are set to be required, then you can just focus on the ones that are actually required. Then using that information, focus on the form fields in the submission that specifically correlate to the required Laserfiche fields.

0 0
replied on January 23, 2015

It did turn out to be that a field was required on a template that the save to repository process was using. I did not even know the error was referring to the save to repository process, I thought it was talking about the form fields. It was a very confusing message for sure. Most all Laserfiche applications do not allow you to configure a template without a required field populated, this would be helpful in the forms choose fields window.

0 0
replied on January 23, 2015

The stack trace in the error message can usually give you a hint as to where the issue lies

Laserfiche.Forms.CommonUtils.LFHelper.SetValueToTemplateField

So with that, it could lead you to reviewing where you have mapped the form fields to the Laserfiche fields.

Another thing that's useful is to have an understanding of the Laserfiche error codes. Error codes of the 9xxx range indicate it's coming from the Laserfiche Server (versions 8 and 9 for now). You can review this page for more information about our error codes.

I'll pass along the suggestion of having the "Configure Fields" dialog in Forms indicate whether a field is required.

0 0
replied on January 23, 2015

Do you have any custom javascript running on the Form?

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

Sign in to reply to this post.

Details
Related Posts
Loading ...