QuickLookup v1.0.2 - Display multiple fields in "I2 Which Field" not functioning properly.

[bottomlinebrokers]

I installed QuickLookup v1.0.2 into my Summer '22 sandbox development org. I am attempting to use the features described here (
https://unofficialsf.com/new-option-for-the-lookup-component/ ) to display multiple fields on a record in the Lookup dropdown while searching on the Name field.

Per the page, I have to provide “I2_Display Which Field?” a formula field with the multiple fields to display in the dropdown
and “I8_Search this Field instead of Display Field” the field to search on.

I've embedded the component in my screen flow (running under API 55). The I8 portion works; I provide a fieldname (custom or standard) and Quick Lookup will search on it. Providing I2 a single field name, or a formula (or text) field containing a SINGLE fieldname works as well. It will search on the I2 entry, and display the I8 entry.

Steps to Reproduce

Attempt to expand the formula for I2 to display multiple fields. It simply displays nothing:

I am attempting to search on the Opportunity object. My formula field for I2 was:

"Name + Property_City__c + Listing_Number__c + StageName"
(Note: Name and Property_City are text fields. StageName is a picklist. Listing_Number__c is an autonumber field, but that should be text)

I also attempted these derivations in the formula:

"Name, Property_City__c"
"Name Property_City__c"
"Name | Property_City__c"
"Name" + "Property_City__c"

I also tried these derivations in a Text field rather than a formula field

Name, Property_City__c
Name Property_City__c
Name | Property_City__c
Name + Property_City__c

Please assist. In this flow, our users will have to choose among several Opportunities that are named the same, but are in different cities or have a different Listing number.

Thank you!

Mark

[ericrsmith35]

I'm assuming that you have created a formula field on the Opportunity object and are putting that field API name into I2.

That said, the formula should be "Name & Property_City__c & Listing_Number__c & TEXT(StageName)"

[bottomlinebrokers]

No, I created the formula field inside the flow and attempted to use that. I didn't think I would need to store this as data on a record, as this type of display is only used in this flow. Is this incorrect?

…

________________________________ From: Eric Smith ***@***.***> Sent: Tuesday, June 14, 2022 4:43 PM To: alexed1/LightningFlowComponents ***@***.***> Cc: Mark Pieter ***@***.***>; Author ***@***.***> Subject: Re: [alexed1/LightningFlowComponents] QuickLookup v1.0.2 - Display multiple fields in "I2 Which Field" not functioning properly. (Issue #1137) I'm assuming that you have created a formula field on the Opportunity object and are putting that field API name into I2. That said, the formula should be "Name & Property_City__c & Listing_Number__c & TEXT(StageName)" — Reply to this email directly, view it on GitHub<#1137 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKNO7TAKI36DUAHFRL3P6HDVPEKLHANCNFSM5YZJXCKA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[ericrsmith35]

The component is designed to work with an actual field on the record.

…

On Tue, Jun 14, 2022 at 7:45 PM Mark Pieter ***@***.***> wrote: No, I created the formula field inside the flow and attempted to use that. I didn't think I would need to store this as data on a record, as this type of display is only used in this flow. Is this incorrect? ________________________________ From: Eric Smith ***@***.***> Sent: Tuesday, June 14, 2022 4:43 PM To: alexed1/LightningFlowComponents ***@***.***> Cc: Mark Pieter ***@***.***>; Author ***@***.***> Subject: Re: [alexed1/LightningFlowComponents] QuickLookup v1.0.2 - Display multiple fields in "I2 Which Field" not functioning properly. (Issue #1137) I'm assuming that you have created a formula field on the Opportunity object and are putting that field API name into I2. That said, the formula should be "Name & Property_City__c & Listing_Number__c & TEXT(StageName)" — Reply to this email directly, view it on GitHub< #1137 (comment)>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AKNO7TAKI36DUAHFRL3P6HDVPEKLHANCNFSM5YZJXCKA >. You are receiving this because you authored the thread.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub <#1137 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF4UHXZH5YFNER3AOICGQO3VPEKQ3ANCNFSM5YZJXCKA> . You are receiving this because you commented.Message ID: ***@***.***>

[bottomlinebrokers]

Well then, that will hopefully solve my problem...I will try now!

________________________________ From: Eric Smith ***@***.***> Sent: Tuesday, June 14, 2022 4:49 PM To: alexed1/LightningFlowComponents ***@***.***> Cc: Mark Pieter ***@***.***>; Author ***@***.***> Subject: Re: [alexed1/LightningFlowComponents] QuickLookup v1.0.2 - Display multiple fields in "I2 Which Field" not functioning properly. (Issue #1137) The component is designed to work with an actual field on the record.

On Tue, Jun 14, 2022 at 7:45 PM Mark Pieter ***@***.***> wrote: No, I created the formula field inside the flow and attempted to use that. I didn't think I would need to store this as data on a record, as this type of display is only used in this flow. Is this incorrect? ________________________________ From: Eric Smith ***@***.***> Sent: Tuesday, June 14, 2022 4:43 PM To: alexed1/LightningFlowComponents ***@***.***> Cc: Mark Pieter ***@***.***>; Author ***@***.***> Subject: Re: [alexed1/LightningFlowComponents] QuickLookup v1.0.2 - Display multiple fields in "I2 Which Field" not functioning properly. (Issue #1137) I'm assuming that you have created a formula field on the Opportunity object and are putting that field API name into I2. That said, the formula should be "Name & Property_City__c & Listing_Number__c & TEXT(StageName)" — Reply to this email directly, view it on GitHub< #1137 (comment)>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AKNO7TAKI36DUAHFRL3P6HDVPEKLHANCNFSM5YZJXCKA >. You are receiving this because you authored the thread.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub <#1137 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF4UHXZH5YFNER3AOICGQO3VPEKQ3ANCNFSM5YZJXCKA> . You are receiving this because you commented.Message ID: ***@***.***>

— Reply to this email directly, view it on GitHub<#1137 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKNO7TF2RASUIFE4SJ6N5BLVPEK7TANCNFSM5YZJXCKA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[bottomlinebrokers]

Eric,

Using a formula field on the Opportunity object was also unsuccessful.

I attempted 3 formulae:

1 - "Name & Property_City__c & Listing_Number__c & TEXT(StageName)", see Error 1.png
2 - "Name " & "Property_City__c " & "Listing_Number__c " & "TEXT(StageName)", see Error2.png
3 - "Name," & "Property_City__c, " & "Listing_Number__c, " & "TEXT(StageName)", see Error3.png

Next steps?

[ericrsmith35]

When you are creating your formula field on the Opportunity object, do not manually type in the field names, operators or functions. Always use the Insert Field , Insert Operator and Insert Selected Function buttons so the syntax is correct.

[bottomlinebrokers]

The formula as your specified originally did not work. Here is what did work, exact copy/paste: Name & ", " & Property_City__c & ", " & Listing_Number__c & ", " & TEXT(StageName) I chose ',' characters as delimiters, because they were most natural on the eye. FYI, I upgraded to v1.0.3 Mark

…

________________________________ From: Eric Smith ***@***.***> Sent: Thursday, June 16, 2022 5:46 AM To: alexed1/LightningFlowComponents ***@***.***> Cc: Mark Pieter ***@***.***>; Author ***@***.***> Subject: Re: [alexed1/LightningFlowComponents] QuickLookup v1.0.2 - Display multiple fields in "I2 Which Field" not functioning properly. (Issue #1137) When you are creating your formula field on the Opportunity object, do not manually type in the field names, operators or functions. Always use the Insert Field , Insert Operator and Insert Selected Function buttons so the syntax is correct. — Reply to this email directly, view it on GitHub<#1137 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKNO7TGW3HWZ4YJPAVKDJRDVPMO3DANCNFSM5YZJXCKA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[alexed1]

What would be a good resolution for this? Is this something we should post about? Or just close it as a case of 'formulas can be tricky to get right'?

[bottomlinebrokers]

Alex,

No...it's not just "formulas can be tricky". The formula format on the original page (https://unofficialsf.com/new-option-for-the-lookup-component/) does not match the formula format that I got to work. So I suspect that the formula example on the page is incorrect. I would suggest somebody edit the original page with 2 or 3 examples of formulae that actually work. You can try mine above...they are in production now.

Thank you for following up!

Mark