need details on event.target.getSelection()

Question

need details on event.target.getSelection()

padmaneela123 opened this issue 3 years ago · 6 comments

in handleLookupSelectionChange(event) all I am getting is selected ID but not complete object attribute/field values. I have situation on parent we have two lookups I want check based sObjectType value I want to call different APEX method. Please advise.

Answer 1 · 2022-06-08T12:12:38.000Z

HI @padmaneela123, I'm not sure to fully understand your use case.
If I get this right, you need to pass extra data to the search handler. This is documented here: Passing custom data to JavaScript and Apex

Answer 2 · 2022-06-08T16:01:30.000Z

Thanks Philippe for the quick response. In my requirement on page i add two lookup fields , one is to select User and other one is badge. Now in handleLookupSelectionChange(even) method event.detail is giving associated selected records ids . but I want to retrieve sObjectType but I am not able to succeed it most likely CustomEvent of selectionchange is just returning selected ids could be possibility . but in the documentation below I read that I can pull all the fields of LookupSearchResults. // Or, get the selection objects with ids, labels, icons... const selection = event.target.getSelection(); Would you please help me to extract data from selection . Thanks Padma.

…

On Wed, Jun 8, 2022 at 8:12 AM Philippe Ozil ***@***.***> wrote: HI @padmaneela123 <https://github.com/padmaneela123>, I'm not sure to fully understand your use case. If I get this right, you need to pass extra data to the search handler. This is documented here: Passing custom data to JavaScript and Apex <https://github.com/pozil/sfdc-ui-lookup-lwc#passing-custom-data-to-javascript-and-apex-optional> — Reply to this email directly, view it on GitHub <#106 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AV2HTQB4JYHGLBWQ4EBF4T3VOCE4DANCNFSM5YESQBBA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

Answer 3 · 2022-06-08T16:30:55.000Z

Ok, now I understand a bit better.

If you're working with different objects in separate lookups, I would advise you to create different handleLookupSelectionChange methods and dedicated Apex search endpoints so that there's no confusion on the object types.

<c-lookup
  onsearch={handleSearchUser}
  onselectionchange={handleUserSelectionChange}
  label="Search for a user">
</c-lookup>
<c-lookup
  onsearch={handleSearchBadge}
  onselectionchange={handleBadgeSelectionChange} 
  label="Search for a badge">
</c-lookup>

If you really don't want to do this then, proceed with my initial suggestion and add a custom data attribute (data-type in the example below) that gives you the object type.

<c-lookup
  onsearch={handleSearch}
  onselectionchange={handleSelectionChange}
  label="Search for a user"
  data-type="User">
</c-lookup>
<c-lookup
  onsearch={handleSearch}
  onselectionchange={handleSelectionChange} 
  label="Search for a badge"
  data-type="Badge">
</c-lookup>

Then, figure out the object type in JS:

handleSelectionChange(event) {
    const lookupElement = event.target;
    alert(lookupElement.dataset.type); // User or Badge
}

Answer 4 · 2022-06-08T16:36:54.000Z

Thanks Philippe . I will try this. Thanks For the quick response. Thanks Padma.

…

On Wed, Jun 8, 2022 at 9:31 AM Philippe Ozil ***@***.***> wrote: Ok, now I understand a bit better. If you're working with different objects in separate lookups, I would advise you to create different handleLookupSelectionChange methods and dedicated Apex search endpoints so that there's no confusion on the object types. <c-lookup onsearch={handleSearchUser} onselectionchange={handleUserSelectionChange} label="Search for a user"></c-lookup><c-lookup onsearch={handleSearchBadge} onselectionchange={handleBadgeSelectionChange} label="Search for a badge"></c-lookup> If you really don't want to do this then, proceed with my initial suggestion <https://github.com/pozil/sfdc-ui-lookup-lwc#passing-custom-data-to-javascript-and-apex-optional> and add a custom data attribute (data-type in the example below) that gives you the object type. <c-lookup onsearch={handleSearch} onselectionchange={handleSelectionChange} label="Search for a user" data-type="User"></c-lookup><c-lookup onsearch={handleSearch} onselectionchange={handleSelectionChange} label="Search for a badge" data-type="Badge"></c-lookup> Then, figure out the object type in JS: handleSelectionChange(event) { const lookupElement = event.target; alert(lookupElement.dataset.type); // User or Badge} — Reply to this email directly, view it on GitHub <#106 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AV2HTQBLCWI2LJBSD5DWKQTVODDEXANCNFSM5YESQBBA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

Answer 5 · 2022-06-08T18:22:37.000Z

Thanks Philippe. I went ahead with a separate selection method. Now the challenge I have is , when I send event.detail value to apex i am getting below error , i changed it Id same error. Lookup error {"status":500,"body":{"message":"Value provided is invalid for action parameter 'recipientID' of type 'String'"},"headers":{}}

…

On Wed, Jun 8, 2022 at 12:36 PM Padma ***@***.***> wrote: Thanks Philippe . I will try this. Thanks For the quick response. Thanks Padma. On Wed, Jun 8, 2022 at 9:31 AM Philippe Ozil ***@***.***> wrote: > Ok, now I understand a bit better. > > If you're working with different objects in separate lookups, I would > advise you to create different handleLookupSelectionChange methods and > dedicated Apex search endpoints so that there's no confusion on the object > types. > > <c-lookup > onsearch={handleSearchUser} > onselectionchange={handleUserSelectionChange} > label="Search for a user"></c-lookup><c-lookup > onsearch={handleSearchBadge} > onselectionchange={handleBadgeSelectionChange} > label="Search for a badge"></c-lookup> > > If you really don't want to do this then, proceed with my initial > suggestion > <https://github.com/pozil/sfdc-ui-lookup-lwc#passing-custom-data-to-javascript-and-apex-optional> > and add a custom data attribute (data-type in the example below) that > gives you the object type. > > <c-lookup > onsearch={handleSearch} > onselectionchange={handleSelectionChange} > label="Search for a user" > data-type="User"></c-lookup><c-lookup > onsearch={handleSearch} > onselectionchange={handleSelectionChange} > label="Search for a badge" > data-type="Badge"></c-lookup> > > Then, figure out the object type in JS: > > handleSelectionChange(event) { > const lookupElement = event.target; > alert(lookupElement.dataset.type); // User or Badge} > > — > Reply to this email directly, view it on GitHub > <#106 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AV2HTQBLCWI2LJBSD5DWKQTVODDEXANCNFSM5YESQBBA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

Answer 6 · 2022-06-14T19:43:50.000Z

Thanks for the details.