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

Discussion

Discussion

FEATURE REQUEST: Ability to insert the same field multiple times on a Laserfiche Template

Laserfiche Ideas Self-Hosted Version 12 Feature
Updated one day ago
posted on February 16

Laserfiche Repository Web Client - 12 (12.0.2510.1022)

Laserfiche Repository Access - 11.1.2509.684

We would love the ability to use the same field, multiple times. NOT a multi value field, but being able to separate it out.

For example: We have three types of addresses - addresses dynamically populated using GIS, addresses that are historical and do not exist in GIS, and intersections only.

Our addresses are broken out into Street Number, Street Direction, Street Name, Street Suffix, Unit Number.

I show/hide based on if the user picks regular address, historic address, or intersection. BUT, I would like this data to be using the same field, so when a member of our community searches for the address, a street name is a street name, no matter the address type.

  

0 0
replied on February 17

Hopefully this helps. From an internal perspective, we are looking to capture 3 different "types" of addresses, but when a (public) user searches for a street name using Weblink, it shouldn't matter if it was an intersection, an address that doesn't exist in GIS, or one that does. I know there has to be some other way to deal with this in addresses, but the big thing is that we dynamically populate the addresses using our GIS as much as possible, but sometimes they don't exists. Please see attached.

Same Fields Feature Request.pdf (200.95 KB)
Download
1 0
replied on February 17

Ok, I understand the problem now. It will take some playing with, but you can actually construct your own search syntax in Weblink. I think you'll want something like this:
 

Create search form with custom fields for address fields. Current/Historical addresses have the same fields. We want to map on search field to either of two fields Current or Historical.



Then you can build your search something like this


Now your intersections, assuming all documents have it can be included as direct field searches below and appended to the query!

It might not be perfect, but should get you closer to what you're looking for.

2 0
replied two days ago

Actually, could you combine all of your fields including address type into one multi-value field group? You could still use field rules to show/hide intersection, but your other two address fields are identical outside of labeling which would be handled by the address type dropdown.

1 0
replied one day ago

Not quite. If we take intersections out, the other two are identical EXCEPT one is pulling data from GIS and populating and the other is a free text fields because it is an address that no longer exists.

0 0
replied on February 17

Why can't you just use the one field there? I'm assuming you are changing the field label so the user can see "hey this is a historical address not an intersection". Could you just use the new "static text" field to have each of you three address type names that denote the description of the field below it? The static text fields could be toggled by field rules where the address fields stay the same.

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

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...