I have a form created that populates from a stored procedure. The data populates fine however as soon as it has populated it blanks out (see two screenshot). It is intermittent and has no pattern as to why it may be doing this. We are on Forms 10.1.0.642 ... Any ideas anyone please? Thanks
Question
Question
Data fields populated by Lookup vanish after form load is complete
Replies
How do you configure the lookup rules? can you take a screenshot of them? Also you can use Chrome Developer tools to capture the network request open a support case with your VAR by providing the download process /screenshot for lookup rules/network requests when reproduce the issue so that we can check what cause this.
The rules were entirely javascript, but as mentioned earlier reply the issue seemed to be the multiple parameters used in URL:
I had:
http://laserfiche-test..../Forms/CRD?RowID=66DAF773-365E-4E04-858B-2341E680CAE2&Type=MC
it worked when changed to:
http://laserfiche-test.../Forms/CRD?RowID=66DAF773-365E-4E04-858B-2341E680CAE2-MC
not sure why though!
I didn't see your form has RowID and Type fields, are them hidden? Your JavaScript is to check the value of these two fields then populate other fields with values? There maybe timing issue as the value passed in the URL are processed one by one.
Yes there is a section at the bottom which has a few parameter fields and these two are in there ... they are both NOT read-only and text fields, yes it seems that RowID is populated or a while but Type ID is not then TypeID is populated and goes through the cycle again and the text vanishes. Really bizarre
If the issue can be recreated without customize JavaScript, can you open a support case with you VAR by providing the exported process and the screenshot for lookup rules configuration and the video of steps to reproduce the issue? We can do further trouble shooting with your process.
Ok will do.
This is usually caused by conflicting lookup rules.
I recreated the whole form and only used Field rules and the issue remained, however ... the real issue was not the rules, it was the for some reason the input parameters used in the URL. I had to parameters coming in from the URL, as soon as I chose one the issue did not re-occur! Perhaps a bug? But I am happy as fixed it by trail and error.