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

Discussion

Discussion

Lookup Overrides Drop Down Values

Forms Version 10
Updated October 4, 2019
posted on September 20, 2016

When I perform a lookup to populate a drop-down, the lookup overrides the drop-down list with the values from the lookup.

Even when I have the values in the drop-down list set to match the values from the lookup, it still overrides and prevents me from selecting a different option. 

I know this feature has been requested before, but am wondering if this is available yet. 

I already have the work around implemented by using JavaScript, but am needing to set up the form in a way that allows our customers to manage this form without knowing JavaScript.

 

0 0
replied on October 4, 2019

This post is similar to the post below, so I won't ask this again but if anyone has a solid resolution for this please check out the link below and my issue I explained. Thanks!

DB Lookup makes Drop-Down values disappear https://answers.laserfiche.com/questions/100142

 

0 0
replied on September 22, 2016

This feature is not been implemented yet and there is no plan to add support for it in Forms 11 due to the implementation may affect the stability for lookup(see https://answers.laserfiche.com/questions/100142/DB-Lookup-makes-DropDown-values-disappear), can you share what is the use case to retain the choices after lookup for dropdown?

 

0 0
View 4 previous replies
replied on September 22, 2016

Xiuhong Xiang... this issue has existed since the original Forms release back in 8.3. It's disappointing that it is treated as a low priority issue.

The primary use case for us is letting an anonymous user change their selections on a form they have submitted.

Let's say that it's an event registration form that asks the person what they want for lunch during the event. There are three options: chicken, steak and lasagna. The user picks chicken and submits the form. Workflow assigns a unique token (a GUID) to the submission and stores the values in an external table. Then it sends the user a link saying "thank you for registering, if you change your mind here's the link to the form" and the URL has the unique token embedded, which does a lookup on the external table and populates the fields with their previously entered data.

The issue now is that when the user reopens that form to change their lunch selection to "steak," the dropdown contains only "chicken".

Obviously this is a simplistic example, but it illustrates several VERY COMMON use cases for our clients. We use a similar process to send resubmission links to anonymous users for job application forms, insurance forms, customer survey forms, and more. On all of our forms, and for every single dropdown field, we have a hidden "master" field that is static and not tied to lookups. We then copy the rest of the values to the user-facing dropdown field after the lookup completes. This increases the size of the forms significantly and adds a lot of complexity.

0 0
replied on September 23, 2016

Just posting to say I agree.  We are using this activity very frequently and the difficulty of implementing this seems to really bog us down.

0 0
replied on September 29, 2016

Append choices to lookup result will be supported in Forms 11.

1 0
replied on October 20, 2017

We need to have this working ASAP. If we can't get this to work, client may walk away from Laserfiche

0 0
replied on April 2, 2019

Has this been resolved? I am experiencing a similar issue in 10.3.1.635

0 0
replied on April 2, 2019

Hi Christian,

Support append defined choices to lookup results was added since Forms 10.2, you need to check the option from the drop-down field.

Can you please check whether you have enable that option?

1 0
replied on April 9, 2019

Yes, the option is enabled, but drop-downs that are filled via a lookup rule are still limited to the single derived value - the appended values are not present once the lookup rule fires. 

1 0
replied on September 20, 2016

This was fixed for us.  Are you running Forms 10.1 with both released updates?

0 0
View 3 previous replies
replied on September 20, 2016

We have both updates installed and it still happens. We had to come up with a pretty nasty and complicated workaround for it.

0 0
replied on September 20, 2016 • Show version history

Yes, we are on Forms 10.1

0 0
replied on September 21, 2016 • Show version history

We have had to come up with tons of workarounds as well.  It seems to work but only in certain scenarios.  Going to sound weird, but try to put the field in a Collection.  

For example I have a field called Gender.  It is a list of all the Gender options at a client (Male, Female, Other, etc).  We have a lookup rule that fills that list but also a lookup rule that populates the gender of the current person we are looking at.  We are able to get it to work if it is in a Collection.  

0 0
replied on September 21, 2016

Yeah, it works fine inside collections. Outside though the values get overridden by whatever single value is coming from the lookup.

0 0
replied on September 21, 2016

Have you been able to get a field to populate based on a lookup from two other fields populated by a stored procedure?

 

We have a stored proc returning an id and location.  We want a third field to fill in with a vendor based on the other two.  Still can't get it to work.  Works fine if you type in the ID and then type in the location, but populating from a stored proc doesnt seem to work.  

0 0
replied on September 21, 2016

I tried putting it in a collection. Still did not work.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...