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

Question

Question

Dynamic field not displaying in web access (web client)

Web Client Version 10
Updated September 28, 2018
asked on January 19, 2018

I have a template with a field for the document owner.  I recently set that field to be dynamic, the same as I've used that field in other templates to identify the document owner. (see attached)

But, the behavior I'm getting in Web Client is that it shows as 'Loading' with a spinning progress icon and never brings back any values to populate the drop down.

This is in contract to the preview in the Admin console where I can see drop down content AND in the LF desktop client where I can also get the lookup to populate the dropdown.  Looking for some assistance with why this is not populating correctly.

I have exited the session, rebooted the computer, had another user attempt to view the drop down on another workstation and it is consistently showing as 'Loading' in all scenarios.

corp dynamic field not working.docx (615.31 KB)
Download
0 0

Answer

SELECTED ANSWER
replied on September 27, 2018

Hi Michelle, 

 

I created a template following your instructions, and I can reproduce the issue in Web Client 10.2.0.150. I found that, in order to reproduce the issue,  the dynamic lookup field must be ordered after the groups fields in template. Dynamic fields located before the group field load fine.

 

The good news is this bug matches the description for SCR155239, which was fixed in Web Client 10.2.1. I double checked and confirmed that I cannot reproduce the issue with same template in Web Client 10.2.1 or 10.3.1. 

 

Upgrading to Web Client 10.2.1 or later should resolve the issue for you. 

2 0

Replies

replied on September 24, 2018

We are still on version 10.2 (10.2.0.150) and problem persists.  But, I believe I have found what is causing it.  The template in question has two multi-value fields which are grouped in a field group, in addition to the dynamic field used to select document owners from a SQL table.

When I recreated the template from scratch and included all the fields (before grouping any of them) the drop down for the document owner field works fine.  Once I put the two fields into a field group, it 'broke' the dynamic lookup field.

'Broke' means that the icon spins and says "loading . . ." while showing a blue bar in the field that doesn't allow you to do anything using either the drop down or via manual entry.

Can anyone replicate this in 10.2 or in 10.3?

1 0
SELECTED ANSWER
replied on September 27, 2018

Hi Michelle, 

 

I created a template following your instructions, and I can reproduce the issue in Web Client 10.2.0.150. I found that, in order to reproduce the issue,  the dynamic lookup field must be ordered after the groups fields in template. Dynamic fields located before the group field load fine.

 

The good news is this bug matches the description for SCR155239, which was fixed in Web Client 10.2.1. I double checked and confirmed that I cannot reproduce the issue with same template in Web Client 10.2.1 or 10.3.1. 

 

Upgrading to Web Client 10.2.1 or later should resolve the issue for you. 

2 0
replied on September 28, 2018

Ryan,  many thanks for the time to reproduce my issue.  I will see about relocating that field prior to the field group to correct the issue for now.

We are looking to upgrade, so I am also glad to hear that this does not continue to be an issue beyond the 10.2.0.150 version.

Thank you again!

0 0
replied on January 21, 2018

Hi Michelle,

As I can understand, the problem exists only in "Web Client", so the Dynamic Fields is working properly in Laserfiche Client (Desktop version); right?

If so:

  1. Can you try creating another test template with a dynamic field, but use another source table containing a lower number of rows (~10). If it works fine in Laserfiche Web Client, so the big number of rows may be the reason.
  2. Which version of Laserfiche Web Client are you using? Because it's working fine for me on version 10.2 (10.2.1.277) with 600+ rows.

Good luck,

0 0
replied on January 22, 2018

As I can understand, the problem exists only in "Web Client" (this is correct), so the Dynamic Fields is working properly in Laserfiche Client (Desktop version); right? Again correct

If so:

  1. Can you try creating another test template with a dynamic field, but use another source table containing a lower number of rows (~10). If it works fine in Laserfiche Web Client, so the big number of rows may be the reason. Test template with document owner field setup and set to access same SQL table used in my Corp Admin template.  Field lookup works in Web Client for this test template.
  2. Which version of Laserfiche Web Client are you using? Because it's working fine for me on version 10.2 (10.2.1.277) with 600+ rows. Still on version 10.2 (10.2.0.150)
0 0
replied on January 22, 2018 • Show version history

Hi Michelle,

We also get this issue with the parent field in the Web Client (including version 10.3).

We have a choice of  3 parent fields that then contain fields that can load up to 90k+ values (with a total 180k).

They seemed to have sorted out the issue on the client but no such luck on web yet. 

0 0
replied on January 22, 2018

Alex,  so what you're seeing even in the 10.3 Web Client is that it can't handle lookup fields with very large tables?  You mentioned yours have 90k+ values, mine has maybe a 1,000 so very small in comparison.  As mentioned above, I can get same field with same dynamic setup to work correctly in other templates, just not this one.  Thinking my best bet may be to recreate this as a new template and use Workflow to replace the template on all the docs.

0 0
replied on January 25, 2018 • Show version history

Michelle: I was unable to reproduce your issue using 10.2.0.150. I would try upgrading to the latest 10.2.1 web client before using your workflow workaround (it's a good idea, but hopefully not needed). If upgrading to 10.2.1 doesn't work, you can ask your VAR to open a support case so we can get to the bottom of the issue.

 

Alex L.: The issue you are experiencing sounds performance related, and maybe not related to Michelle's issue. I would encourage you to also open up a support case if you continue to experience problems.

 

Henry: Thanks for chiming in! Always good to see the community getting involved.

0 0
replied on January 26, 2018

Alex K, I am scheduling an upgrade to 10.2.1 for February.  I will see if that addresses the issue and update this thread.  Hopefully I won't need to open a support case or use the workflow workaround! 

Thanks for all the responses, ALWAYS appreciate the support from Fiche Friends and Laserfiche staff.

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

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...