I'm experiencing an issue where dynamic fields do not show as a list type, and therefore do not populate the possible values. The template dynamic fields work fine in laserfiche, but not in the laserfiche scanning app.
Question
Question
Laserfiche Scanning - Dynamic Fields not showing as list, not populating
Answer
If this is version 9.0.3, then, yes, it is a known issue. If it's anything lower or higher, then please have your reseller open a support case.
Thanks for the update. We are using 9.0.3, is there an available hotfix? This is a pretty serious bug for us since the purpose of the dynamic fields is to make it "human-proof" when indexing during scans...
There isn't a hotfix for 9.0.3. You can roll the Client/Scanning installation back to 9.0.2 or upgrade the server and clients to 9.1.
Understood. Generally we document these cases by referencing changelogs or KB's, but I'm unable to find this dynamic field/scanning problem in 9.0.3 known issues, nor 9.1 release notes. Can you point me in the right direction?
https://support.laserfiche.com/KB/1013369
https://support.laserfiche.com/KB/1013325
It looks like the list of fixes for 9.1 is missing Scanning fixes. We'll get that sorted out.
I encountered this at one of my implementations. We were told by Laserfiche that this aspect has been tightened down on. They no longer allow the use of Dynamic Fields with a drop list as of 9.1. It completely shut down one of my departments. I did find a work around that works, and that Laserfiche approved as one option they would have recommended, we were greatly affected because we were using the list inside of Quick Fields for accuracy in pattern matching. Let me know if you want further details.
To clarify, there are two issues being mentioned in this Answers thread:
- There is a known issue in Laserfiche Scanning 9.0.3 where dynamic fields didn't work, even if it is correctly configured in the Laserfiche Administration Console.
- A valid configuration for dynamic fields requires that the Laserfiche Fields be of the type, "Text" and not of the type, "List"
Laserfiche Support has seen an influx of dynamic field related cases and the root cause is because the Laserfiche Field type was "List." Please make sure to set the field type to "Text" when making the field a dynamic field.
As for my issue, I can confirm that updating to 9.1.1 fixed the scanning dropdown issues.
Thanks Alex for that clarification in regards to my response. They stated "list type" so I wanted to be sure they did not have the field set to "list type" to try to prevent any complications in the future if that's what was truly meant. :)
Replies
This is a known issue. Dynamic fields that rely on parent values will not properly populate in LF Scanning.
Hi, I have the same issue and being that it is a known issue, I upgraded to the 9.1. I am still having this problem. So, is there a way to fix it? Thank you so much.
Jen