Anyone else ever experience issues where a form that is submitted has all the data in Forms, and is filled out properly, but when stored in Laserfiche, there is no template or metadata assigned? It happens to us occasionally where the document get's stored in Laserfiche after it's submitted, but there's no template assigned even though in our Process Modeler, we have all the info being mapped correctly. It's random, but curious if anyone else ever has it. Not sure if it's related to a sequence of how the end user is filling out the form and submitting, etc. Thanks!
Discussion
Discussion
Typically this would occur if the form field data that's mapped to the Laserfiche field exceeds the field width. This can also occur when the Laserfiche field is required, but there's no form field data mapped to it. Forms 9.2.1 addresses the second matter by now indicating which Laserfiche fields are required.
Hello Daryl,
When this issue occurs, you can try to check the Application Event Log to see if any kind of error was reported which may be able to better point at perhaps what could have went wrong.
Regards,
Andrew
What version of Forms are you using?
Forms 9.1...we still can't upgrade them to 9.2 because there is a bug with having Forms Server and LF Server on 2 different domains.
Forms 9.2.0 used to have issue when Forms Server and LF Server on 2 different domains, the issue should be fixed in 9.2.1, can you try with 9.2.1. If there is still issue with 9.2.1, please contact support so that we can address the issue for you.
Can you confirm if this has been tested? We can't afford for their Forms Server to be down since the Form is used by the Public. I don't want to assume it is fixed unless there is some level of confirmation that Laserfiche has tested this. There was an open case for this with an SCR and I was told I would be notified when this issue had been fixed, I've yet to be notified other than this post. Thanks!
Still waiting to hear if there is confirmation that the 9.2 bug for having Laserfiche Server and Forms Server on 2 different domains has been tested and confirmed fixed before assuming and upgrading and creating a potential issue. Thanks!