+1 800 985 8533Contact Us
Tech Tip: Laserfiche 8.2 Preview: Dynamic Fields | Laserfiche News Portal

Tech Tip: Laserfiche 8.2 Preview: Dynamic Fields

Note: Starting today and continuing over the next few Tech Tips, we will be previewing new features coming in Laserfiche 8.2. Since this is a preview, note that the details and appearances of certain elements may change between now and the final release.

*****

Laserfiche 8.2 introduces dynamic fields, which allow you to link fields together such that selecting a value in one field determines what values are available in another. Dynamic fields are especially useful if you have templates with fields whose information naturally relates to each other.

For example, Gary is a hiring manager for Roth Equity and he uses Laserfiche to organize applications submitted by prospective hires. When an application comes in, he assigns a template that includes fields for the applicant’s name, address, and telephone number, as well as the department and position the application is for. Rather than select from the long list of Roth’s open positions each time, Gary creates a set of dynamic fields that will populate the Position field’s list values based on what he selects in the Department field. If he selects the accounting department, for example, only the available accounting positions are listed:

2010-10-18 - Dynamic Fields - Accounting

However, if he selects the legal department, the list changes to display only the available legal positions:

2010-10-18 - Dynamic Fields - Legal

Note: If two fields are part of a dynamic fields set, the child field’s values will not be populated until you have selected a value for the parent field. In the example above, the Department field is the parent field and the Position field is the child field.

Searching with Dynamic Fields

Dynamic fields also carry over to template searches. If a template contains a dynamic fields set, the link between those fields will apply when entering your search criteria. For example, if Gary wants to run a search with his Employment Application template, when he enters a value for the Department field, the search will automatically restrict the Position field criteria to positions in that department.

Note: If a field is part of a dynamic fields set, you can still perform a search using only that field and its values will not be constrained by its relationship to the other fields in the set.

The User Education team at Laserfiche consists of the technical writers responsible for all Laserfiche software documentation, including help files, white papers, and instructional videos.

Comments (All Fields Are Required)

  1. (required)
  2. (valid email required)
  3. (required)
 

    • Daniel O’Leary
    • October 18, 2010 at 4:54 pm

    Will this be part of the toolkit as well?

    • User Education
    • October 19, 2010 at 9:39 am

    The way dynamic fields are configured is by pointing to an external table that defines the parent-child relationship from the Admin Console. And yes, that functionality is part of LFSO also.

    • Sithembiso Ngubane
    • October 21, 2010 at 7:20 am

    I can’t wait for this feature. It’s the best thing since sliced bread. Thanks.

    • Bruce Green
    • October 21, 2010 at 2:26 pm

    Does the Dynamic Fields feature also allow retrieving external database values to populate a single list, thus taking the hassle out of Stored Procedure based list fields?

    • User Education
    • October 22, 2010 at 11:40 am

    Bruce, I’m not quite sure what you mean by “Stored Procedure based list fields,” but yes, dynamic fields will allow you to populate lists with external database values.

    • Richard Caldwell
    • December 28, 2010 at 8:34 am

    Will there be a validation function to search all entries done before establishing Dynamic Fields to confirm compliance to the Dynamic Fields rules?

    • Connie Anderson
    • December 30, 2010 at 12:02 pm

    There isn’t any built in way to validate pre-existing data, no. You might be able to write a script to handle that, though–you could ask on the Support Site forums for help putting something like that together.

    • Jerry Breitbarth
    • January 6, 2011 at 3:42 pm

    Will there be a way to make this parent and child field relationship with an existing Version 8 database that currently has a single field that is the “type” option and 4 different fields that have a type drop-down list for each type? In other words right now there are the following fields: Type, Record Type, Research Type, Services Type, Insurance Type. Right now the template has all 5 fields and you have to choose accordingly. What are my options in Version 8.2?

    • Connie Anderson
    • January 7, 2011 at 11:41 am

    If I understand correctly, what you’re saying is that right now there is a Type list field in which they select Record, Research, Services or Insurance, and then they go to the list field that corresponds to the type they chose and select a sub-type.

    If that’s the case, in Laserfiche 8.2 you could create a template with two dynamic fields. The first would contain the initial set of types (Record, Research, Services and Insurance). The second would contain all of the possible sub-types, but once you selected one of the four primary types, the second field would only display the values for that primary type.

    The important thing to note is that this isn’t going to happen automatically, since dynamic fields are more like table references than existing list fields. You would need to set up an external table with this information, and you might need to use field merging to consolidate your existing information as well. For more details of setting up dynamic fields (including examples), see the Dynamic Fields chapter of the Administration Guide, here: http://www.laserfiche.com/support/webhelp/laserfiche/8.2/en-us/adminguide/lfadmin8_CSH.htm#Dynamic_Fields.htm

    If you need help merging your existing field data, you can always ask on the Laserfiche Support Site forums.

    • Calvin B
    • February 2, 2011 at 2:25 pm

    Can this dynamic list be incorporated between the choice of template and a specific field? ie. Lets say we have a “Bylaw” template and we have a field that identifies types of documents (ie Bylaw – Road Closure, Bylaw – Tax Rate, Agreement – Permanent, etc.). Can we dynamically filter the field that identifies types of documents to only show Bylaw Types (ie Bylaw – Road Closure, Bylaw – Tax Rate) in that field based upon the Choice of the Bylaw template?

    Thanks

    Cal

    • User Education
    • February 8, 2011 at 10:40 am

    Currently the dynamic fields feature is only a function of relationships between fields, and is not related to the template at all.