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

Question

Question

Layout/Modern Designer Lookup Issues

Forms Version 11 Forms Layout Designer
Updated August 1, 2024
asked on August 1, 2024 • Show version history

I have a weird thing happening where I use field rules to hide and show a dropdown list and the lookup stops working.

A lookup runs on the dropdown value and finds the username of the supervisor:


If the checkbox is checked a different dropdown shows:


If I switch back with checkbox unchecked, the lookup stops working. 

Here are the lookups:


I am on Forms 11.0.2311.50553. Is this a bug? Or is this expected behavior on the new layout designer? I copied it directly from the classic designer where it works this way. 

Thanks in advance fellow 'Fichers

0 0

Replies

replied on August 1, 2024 • Show version history

I'm not sure I'm able to reproduce this. What about the lookup stops working? Is it that when you toggle the checkbox back the field doesn't re-populate with the correct dropdowns selected values?

0 0
replied on August 1, 2024 • Show version history

Thanks for asking. When I toggle the checkbox back, nothing populates into the 'Supervisor Username' field any more.

I have 2 lookups pointing to the same results field (username). It's as if when the first lookup runs, it disables the other. 

I can reproduce it going the other way as well, but it's a little different. Where (after refresh), if I click the checkbox first and select from 'Select From All..', as soon as I uncheck the checkbox, ( back to 'Select Supervisor') the lookup doesn't run. 

I can send you pics of what I'm talking about if helpful :) 

Also, no javaScript running on any these fields. 

EDIT: I created a new field to use as username. I pointed the lookup to the new field and the problem persists there too. 

FYI, we can reproduce this on a separate form. Looks like a bug where the lookup locks on the second lookup that populates to any field. Workaround is to have have 2 separate result fields rather than one. Then use a formula logic to populate a 3rd field. 

Still, I don't believe this is expected behavior???
 

0 0
replied on August 1, 2024

I will double check whether or not this is a bug, and how it works on classic forms and get back to you. Thanks for reporting it! We are working on some lookup items for the LF12 release so if it is determined to be a bug we will target it for that release.

1 0
replied on August 1, 2024

Cool, thanks. The work around is minor so not high impact bug...if it is one.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...