I have template with dynamic fields that works on the preview in admin console and in the template when using Laserfiche client, but the list are not showing up in Web Access. When you click on a the parent field in template it shows a blank drop down, but you can see it try's to do a look up and comes back with no values.
Question
Question
Dynamic list field not showing up in Web Access
Replies
Hi All,
I know this is a bit of an old thread but we have encountered this issue in Web Access 10. We have a dynamic field called "Client Name" that is populated from a dynamic linked SQL table, this works fine from the admin console and from the Laserfiche client (9.1 and 10) but not from Web Access 10. Unfortunately removing some of the options from the pick list is not an option for us!
We have even attempted to run the app pool identity's in IIS with the domain admin account which has access to SQL to try and eliminate a permissions issue from Web Access 10.
Has anyone got any idea's??
Thanks
I just looked at document that was already indexed before the dynamic fields were set up, and it actually would show all of the look up values in the child field associated to the parent field that was already indexed. Though in the parent field I could still only see the choice of what was already there, and all others were blank.
What version of Web Access are you using? How many values do you have under your parent field? What browser version are you using?
Hey Mark,
There are no known issues in Web Access 9.1 that match your description, and we haven't had any luck reproducing the issue internally. My recommendation is to open up case with Laserfiche Support.
In the case, be sure to:
1. Include a video reproducing the issue.
2. Include a fiddler (http) trace taken while reproducing the issue.
3. Reference this thread.
Mark,
Please also confirm that the Laserfiche fields you are configuring to be dynamic fields are using the "Text" type and not the "List" type.
I was able to get it working. There was only 2 choices in the parent field but there was about 50+ choices in secondary field. Not really sure what it was because it was always working in the client, but when I deleted about half the choices in the secondary it started working in web access. I then added each one back one by one to the table and it remained working on web access.
Thank you for all your help.