Only Salesforce could make this as difficult as it is. But thank you(!) for not simply repeating the field help that I could read for myself like every other site (including Salesforce help) did.
I was just using this for a lookup on existing accounts function, and couldn't understand it very well till you showed me in the first 2 minutes what I was not understanding. Its the fundamental relationship that exists in a lookup. Thank you sir, look forward to seeing more content.
Thank you! I'd spent too long trying to get this to work, and other "how-to" web pages I found did not explain it as clearly as you did. The key thing is that you're basically just "borrowing" an existing relationship. The really cool thing is that any filters on the lookup relationship you use, are also applied on the screen flow.
Can you demonstrate a flow that pulls information from the Lookup component? Like if I search/lookup a Contact, I am able to pull the related Account information to display on the Screen from that Contact.
hey quick question. So all lookup fields will have this internal lookup field API as (objecttheyarelookingup)ID ? like for account you used AccountId, similarly if I have custom field which is looking up to other custom object say Class then I would use ClassID as Field API Name?
Very well explained, thank you! I've two questions: 1. A self-lookup also works (lookup field on object to itself). Is there a reason why one would not go this route if a lookup relationship does not already exist on the field of interest? 2. A text variable resource was created to store the recordId and entered in the Record Id field of this component. Debugging shows a value for this record in the screen flow but shows as null in a Get element for when records with this id is queried - so it appears that the record selected is not passed to the variable. Any idea on what might be missing in this scenario?
Thanks, this helps a lot! Though, I am confused about the Widget custom object. Why can't the Lookup component reference the Widget object directly? Why do you have to create a reference through an unrelated object?
Hello, thanks for your video, Do you know if it's possible for us to put a default valeur from a picklist when a specific user create an opportunity? For example, we want that when someone from USA create an opportunity, it directly puts USA in the final destination country... If yes, can you please help me? Thank you, Martin
Do you have an idea about how to create an object inside the field if not existing, for example, if a doesn't find an account in the lookup field, he can use a + button to create a new one ?
The lookup component itself doesn't allow for this I believe. I think we still have to use a create element inside the flow. If the the lookup component is blank you could route the user to another screen for them to create the account. You could also ask the user "Do you want to create a new account?" and then use that input to move them to a screen for account creation.
Only Salesforce could make this as difficult as it is. But thank you(!) for not simply repeating the field help that I could read for myself like every other site (including Salesforce help) did.
I was just using this for a lookup on existing accounts function, and couldn't understand it very well till you showed me in the first 2 minutes what I was not understanding. Its the fundamental relationship that exists in a lookup.
Thank you sir, look forward to seeing more content.
Thank you! I'd spent too long trying to get this to work, and other "how-to" web pages I found did not explain it as clearly as you did. The key thing is that you're basically just "borrowing" an existing relationship. The really cool thing is that any filters on the lookup relationship you use, are also applied on the screen flow.
hit a snag and this is exactly what I needed. thanks!
Thank you a lot, i really needed this help to have a look up for Products.
Object API Name: Case
Field API Name: ProductId
Super helpful explanation of a confusing component - Thanks so much!
Much Appreciated!
Thank u so much..its very helpful
Instant subscription to this channel. Good explanation, clear english. Many thanks! Keep em coming!
GREAT explanation at 2:15, thank you!!!
So simple in hindsight but this video saved me.. Thank you!
Excellent, very clear explanation of this odd component.
Can you demonstrate a flow that pulls information from the Lookup component? Like if I search/lookup a Contact, I am able to pull the related Account information to display on the Screen from that Contact.
I really appreciate you! This component is so helpful and I didn't know how to use it before!
Happy to help!
I agree great call out on the user object. Exactly what I was looking for.
Perfect! This was exactly what I was looking for!!!
You just saved me SOOOO much time. I appreciate you! thanks!
Excellent explanation. This can be a pretty confusing component. Thanks!
Great callout regarding the User object
Great explanation. I was struggling to create a Lookup to Users. It was very well explained how to do it. Many Thanks
Thank you so much! It's very helpful!
Super helpful! Thank you!
This video was SO helpful! Thank you!!
Best video of the same topic.
Thanks so much for the great explanation and examples. Very helpful!
Looking forward for more videos like this. You explained it very nicely and showed all examples for different objects that was great
Thank you so much for sharing this very informative video
Nice Explanation !!
Brilliant video, thanks 👍
Thank you! Very helpful
hey quick question. So all lookup fields will have this internal lookup field API as (objecttheyarelookingup)ID ? like for account you used AccountId, similarly if I have custom field which is looking up to other custom object say Class then I would use ClassID as Field API Name?
How to rename or add the existing lookup in edit screen plz tell me urgent
Very well explained, thank you!
I've two questions:
1. A self-lookup also works (lookup field on object to itself). Is there a reason why one would not go this route if a lookup relationship does not already exist on the field of interest?
2. A text variable resource was created to store the recordId and entered in the Record Id field of this component. Debugging shows a value for this record in the screen flow but shows as null in a Get element for when records with this id is queried - so it appears that the record selected is not passed to the variable. Any idea on what might be missing in this scenario?
Ha! Please disregard #2 - I opted to Manually assign variables (under the Advanced dropdown) and now see the value has passed to that variable.
Thanks and awesome question! I don’t think there is a reason not to use a self lookup - seems like it should work fine!
I am trying to get the Case Number as the lookup field. When I run a debug...zero records populate. Any idea why? Thanks!
I really need a 1:1 mentor for creating this flow I need for work. When I have the "resources" to book the session I will. No pun intended.
Thanks, this helps a lot! Though, I am confused about the Widget custom object. Why can't the Lookup component reference the Widget object directly? Why do you have to create a reference through an unrelated object?
Hello, thanks for your video,
Do you know if it's possible for us to put a default valeur from a picklist when a specific user create an opportunity?
For example, we want that when someone from USA create an opportunity, it directly puts USA in the final destination country...
If yes, can you please help me?
Thank you,
Martin
How can I create a lead lookup field
What am I doing wrong? This is not working for me at all.
Wish I could upload a screenshot. Or That Nick had an email I could send a question to.
Can you make videos on project examples in LWC
Do you have an idea about how to create an object inside the field if not existing, for example, if a doesn't find an account in the lookup field, he can use a + button to create a new one ?
The lookup component itself doesn't allow for this I believe. I think we still have to use a create element inside the flow. If the the lookup component is blank you could route the user to another screen for them to create the account. You could also ask the user "Do you want to create a new account?" and then use that input to move them to a screen for account creation.
This has been really helpful. Thank you!