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

Question

Question

metadata template not inheriting from parent folder

asked on June 25, 2015

Using LF 9.2.1, we assigned templates to folders and pre-populated common fields.  Users are then able to reduce their keystrokes filling in fields, however, the new documents imported to those folders don't seem to be inheriting the pre-populated field input - which defeats the purpose of pre-populating.  We tried adding parent token but that is very restrictive as there are cases when there is a valid reason for changing the field input.

I've searched training videos, support site but I haven't found the troubleshooting answer to exactly fit this scenario yet.  We are not using workflows at the moment so looking for another answer.

Your help is greatly appreciated.

 

0 0

Answer

SELECTED ANSWER
replied on June 25, 2015

The %(Parent) token works for me with list fields so I'm not sure what may be causing your the issue you're experiencing. Are you using standard list fields or are these dynamic fields? Here are some screenshots of my setup.

If you need further assistance troubleshooting the issue, I would suggest contacting your Laserfiche reseller to open a support case.

1 0

Replies

replied on June 25, 2015

Hi Shirley,

Can you explain your use case of how documents are being imported and why the parent token may be too restrictive?

Regards

0 0
replied on June 25, 2015

When I did a test field and test template using the parent token in the field, if I imported a new document, the field that contained the parent token was greyed out.  That test template was applied to the folder level but there also greyed out so I couldn't select the proper field information so it would inherit on new documents added.  Basically, couldn't input the field information at any level.

I thought perhaps the parent token had to be applied in the template itself rather than the field but where it indicates Default Value - Add Token, that is greyed out.

New documents are being imported manually to the folder.

Thanks.

0 0
replied on June 25, 2015

Thanks for the clarification. Having the field set with the default value as %(Parent) is the correct procedure. However, I believe the actual issue you're running into is that the user in question that's importing these documents doesn't have the "create" and/or "edit" permission on that specific field.

Make sure the user is allowed the "create" field access right and then when that user imports a new document and assigns that template to the new document, then while the field will still use the default %(Parent) value, the user should now be able to change it should the need arise.

0 0
replied on June 25, 2015

Thank you!  That partially solved the problem when I used the solution on my test field and test template -- if the field was a text field.  But if a List field, it is still not inheriting.  We use several List fields.  Any idea why that is not working for lists?

 

0 0
SELECTED ANSWER
replied on June 25, 2015

The %(Parent) token works for me with list fields so I'm not sure what may be causing your the issue you're experiencing. Are you using standard list fields or are these dynamic fields? Here are some screenshots of my setup.

If you need further assistance troubleshooting the issue, I would suggest contacting your Laserfiche reseller to open a support case.

1 0
replied on June 25, 2015

They are standard lists and I know where I went wrong now!  Thanks so much!

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

Sign in to reply to this post.