Lightning Universal Lookup Component

Helped Solve a Problem

This solved a huge problem in screenflows that the builtin SF version just doesn't handle and that is filtering down the list to only certain records. The only issue I have is having it set to a pre-populated record. Where if I am pulling information from a record, I would like to have it populate with the already set value but it is still changeable if the user needs to make an update. If that could be added, then this app would be absolutely perfect for our needs. We'll still use it, I think, but it may cause some strain to some users.

Great app (before 3.33 update)

When added to a screen flow, this app provides a lot of flexibility to configure how the lookup field functions. However, I updated to version 3.33, and began to experience an issue where the displayed lookup record showed as *mostly* blank on the screen flow, when a value was defaulted into that field. When this occurs, the name of the record is missing, but the icon appeared the same way as if the value was actually present. The lookup field actually still captures that defaulted value, and is able to save it accordingly, but just the displayed name of the record was missing. The issue is sporadic - it happens about 50% of the time, while the other 50%, it displays exactly as expected. This only appeared after installing version 3.33, but never occurred when we were using version 3.31. Other than this issue, this app works great!

Old Api Versions

Would it be possible to update the Api versions of apex to 45.0 or higher? The ICU locale update enforcement for Spring 25 doesn't take effect if you have any apex classes with version 44 or lower and it's causing some bugs. You guys just have one test class at version 42, "LookupResponseTest".

Lookup To User Object in LWR

Great app with many features! We are currently trying to use the lookup component in our LWR site on Experience Cloud. We are trying to do a lookup to the User object and we would like the Name field to be displayed to the user as they are searching. However, it appears that the Nickname field is the one that is displayed and I do not see a way to change this. Is there a way to not show the nickname and instead show the Name?

Issue with 1t. [Child] Dropdown query

Generally speaking, this component works fairly well. It would be nice if the dependentlookup had the same configurable options that the regular one has. The issue I'm having currently with the DependentLookup is that the 1t. [Child] Dropdown query seems to only further filter the 1s. [Child] Query Condition instead of only applying to the initial dropdown display. It works on the Parent one, but not the child. Let's say the parent record has 100 options based on my initial query condition. I put a dropdown query condition in to only show the ones that start with "a" (or whatever). When I click the search box I am presented with 5 (I wish this was configurable as well) options, AND I can still search through the remaining 95 options by typing something. Now, I put similar queries in the child-specific fields. When I click the search box I am presented with the 5 options returned from the 1t. [Child] Dropdown query and can ONLY select one of those. It appears that the query appended to or overwrote the initial query and I now only have a total of 5 records to choose. Searching beyond those values returns no results.

Easy to use but missing "new record"

How do I allow users to create a new record when one isn't found. This functionality would be great.

I have an issue with the component in flow

The lookup icon works fine when used internally but defaults to salesforce icon when used in a public site. For context, I'm using custom:custom47 icon

Has successfully worked in custom Aura Components for several years, does it work for LWC?

This is a great component that we have used since 2020. We are looking to migrate some Aura based custom components to LWC. Does the latest version work with LWC components?

I have a problem when using the component in Screen Flow

Hi, The "Is Required?" condition on the DependentLayout component doesn't work in Screen Flows. When the value is set to {!$GlobalConstant.True}, I see a red asterisk on the field label; however, I am able to proceed to the next screen without selecting any lookup value.

It looks great but I have a Problem

When I'm trying to find CampaignMembers it shows nothing