I'm using the 10.4 Web Client, and I have created a set of templates for my end users.  The templates are assigned to their folders, and the templates have default values on the folder level for the first 5 fields.

So in the template, the default value is set to %(parent) so that when the template is assigned to a document upon import, it should inherit the value already assigned to the parent folder.

This works just fine if I use the desk top client, but we want our users to use the web client and we use Chrome as our browser of choice.  We have the most current Chrome extension so far as I can tell, but that is dated with a year of 2016 in the Chrome store, so it pre-dates 10.4.  I automatically keep my Chrome Browser up to date.

The problem I run into is that I want my end users to set the following option:

Option | New Document | Import Default | <use parent folder's template>.

When I set this initially, it might work for the first drag and drop import I do ("work" is defined as the correct template comes up with the %(parent) default choice filled into the first five fields), but the moment I try a second one, the correct template comes up, but the %(parent) default choice is missing.  But it's also intermittent.  Sometimes it doesn't work even on the first attempt. 

I've not seen this happen when I use the desktop client, so I'm pretty sure the problem is limited to the Web Client, but I don't know if it's a Chrome issue, or on the LF Web Client side. 

I did try with I.E. as well (version 11.0.9600.19377 - the only other browser I have access to) and <use parent folder's default template> does not work at all.  It will not assign a template on the import and I must pick it out manually even though I'd set the option. (I even tried logging out and back in after setting the option. Didn't help.)

So given that the template works in Chrome sometimes, but other times, no, and the setting doesn't seem to work in I.E. (my version) at all, but does work in the Desk Top Client (so far 100% for me), I just have to assume it's browser issues, but maybe correctable in Chrome, with a new Chrome Extension?