Deleted: <p>Salesforce now provides a built-in Lookup component. If that doesn’t meet your needs, you can also consider The powerful <a href="https://unofficialsf.com/lookup/">community Lookup component</a>, which has some additional features.</p><h4><a href="https://help.salesforce.com/articleView?id=flow_ref_elements_screencmp_lookup.htm&type=5">Official Docs</a></h4><p><a href="https://help.salesforce.com/articleView?id=flow_ref_elements_screencmp_lookup.htm&type=5">https://help.salesforce.com/articleView?id=flow_ref_elements_screencmp_lookup.htm&type=5</a></p><h4><a href="https://help.salesforce.com/articleView?id=flow_ref_elements_screencmp_lookup.htm&type=5">Blog Posts</a></h4><p><a href="https://unofficialsf.com/learn-about-the-lookup-component-by-jen-lee/">https://unofficialsf.com/learn-about-the-lookup-component-by-jen-lee/</a></p><h4>Usage Notes</h4><p>There are currently a couple of different approaches you can use for providing Lookup functionality in Flow.</p><h2><strong>The Official Lookup Component</strong></h2><p>The <a href="https://unofficialsf.com/the-new-lookup-component/">official Lookup component</a> that was added in 2019 enables lookup by using object fields of type Lookup. Here are a couple of examples:</p><figure class="wp-block-image size-large"><img class="wp-image-15574" src="https://i0.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-69.png?w=1500&ssl=1" alt="" data-attachment-id="15574" data-permalink="https://unofficialsf.com/?attachment_id=15574" data-orig-file="https://i0.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-69.png?fit=833%2C164&ssl=1" data-orig-size="833,164" data-comments-opened="1" data-image-meta="{"aperture":"0","credit":"","camera":"","caption":"","created_timestamp":"0","copyright":"","focal_length":"0","iso":"0","shutter_speed":"0","title":"","orientation":"0"}" data-image-title="image-69" data-image-description="" data-medium-file="https://i0.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-69.png?fit=300%2C59&ssl=1" data-large-file="https://i0.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-69.png?fit=833%2C164&ssl=1" data-recalc-dims="1" /><figcaption></figcaption></figure><p>In this case, if you want to provide a way for users to lookup Operating Hours, you could use the official Lookup component and reference this field. However, this field is actually part of the Account object. So the configuration of this field would be:</p><figure class="wp-block-image size-large is-resized"><img class="wp-image-15575" src="https://i1.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-70.png?resize=541%2C214&ssl=1" alt="" width="541" height="214" data-attachment-id="15575" data-permalink="https://unofficialsf.com/?attachment_id=15575" data-orig-file="https://i1.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-70.png?fit=707%2C280&ssl=1" data-orig-size="707,280" data-comments-opened="1" data-image-meta="{"aperture":"0","credit":"","camera":"","caption":"","created_timestamp":"0","copyright":"","focal_length":"0","iso":"0","shutter_speed":"0","title":"","orientation":"0"}" data-image-title="image-70" data-image-description="" data-medium-file="https://i1.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-70.png?fit=300%2C119&ssl=1" data-large-file="https://i1.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-70.png?fit=707%2C280&ssl=1" data-recalc-dims="1" /></figure><p>The built-in Lookup Component requires that you specify an existing Lookup field (along with the field’s object). This can require some indirection. For example, if you want to provide lookups to Accounts, you need to find an Account Lookup field on a <span style="text-decoration: underline">different</span> object. </p><p>Fields like OwnerId that can point to more than one object (these are what Salesforce means by ‘polymorphic’ fields) can’t be directly referenced via the built-in Lookup component. Instead of using the Owner field, choose another field which can only be a User, such as CreatedById.</p><h2>The Unofficial Lookup Component</h2><p>There’s also a <a href="https://unofficialsf.com/lookup/">powerful but unofficial Lookup component </a>maintained here at UnofficialSF:</p><figure class="wp-block-image size-large is-resized"><img class="wp-image-15586" src="https://i2.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-71.png?resize=368%2C496&ssl=1" alt="" width="368" height="496" data-attachment-id="15586" data-permalink="https://unofficialsf.com/?attachment_id=15586" data-orig-file="https://i2.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-71.png?fit=483%2C650&ssl=1" data-orig-size="483,650" data-comments-opened="1" data-image-meta="{"aperture":"0","credit":"","camera":"","caption":"","created_timestamp":"0","copyright":"","focal_length":"0","iso":"0","shutter_speed":"0","title":"","orientation":"0"}" data-image-title="image-71" data-image-description="" data-medium-file="https://i2.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-71.png?fit=223%2C300&ssl=1" data-large-file="https://i2.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-71.png?fit=483%2C650&ssl=1" data-recalc-dims="1" /></figure><p>This Lookup component does not attempt to leverage fields of type Picklist. It simply takes an object name and retrieves the appropriate records.</p><p>The Unofficial Lookup Component offers filtering features.</p><p>makes use of direct access.</p><hr /><p><a href="https://unofficialsf.com/the-salesforce-automation-and-decisioning-wiki/about-this-wiki/">About This Wiki</a><br /><a href="https://unofficialsf.com/the-salesforce-automation-and-decisioning-wiki/submission-guidelines/">Contribute to this page!</a></p><div id="like-post-wrapper-154636826-14346-5db5e9bcbbbbb" class="sharedaddy sd-block sd-like jetpack-likes-widget-wrapper jetpack-likes-widget-unloaded" data-src="https://widgets.wp.com/likes/#blog_id=154636826&post_id=14346&origin=unofficialsf.com&obj_id=154636826-14346-5db5e9bcbbbbb" data-name="like-post-frame-154636826-14346-5db5e9bcbbbbb"> </div>
| Added: <p>Salesforce now provides a built-in Lookup component. If that doesn’t meet your needs, you can also consider The powerful <a href="https://unofficialsf.com/lookup/">community Lookup component</a>, which has some additional features.</p><h4><a href="https://help.salesforce.com/articleView?id=flow_ref_elements_screencmp_lookup.htm&type=5">Official Docs</a></h4><p><a href="https://help.salesforce.com/articleView?id=flow_ref_elements_screencmp_lookup.htm&type=5">https://help.salesforce.com/articleView?id=flow_ref_elements_screencmp_lookup.htm&type=5</a></p><h2><strong>The Official Lookup Component</strong></h2><p>The <a href="https://unofficialsf.com/the-new-lookup-component/">official Lookup component</a> that was added in 2019 enables lookup by using object fields of type Lookup. Here are a couple of examples:</p><figure class="wp-block-image size-large"><img class="wp-image-15574" src="https://i0.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-69.png?w=1500&ssl=1" alt="" data-attachment-id="15574" data-permalink="https://unofficialsf.com/?attachment_id=15574" data-orig-file="https://i0.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-69.png?fit=833%2C164&ssl=1" data-orig-size="833,164" data-comments-opened="1" data-image-meta="{"aperture":"0","credit":"","camera":"","caption":"","created_timestamp":"0","copyright":"","focal_length":"0","iso":"0","shutter_speed":"0","title":"","orientation":"0"}" data-image-title="image-69" data-image-description="" data-medium-file="https://i0.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-69.png?fit=300%2C59&ssl=1" data-large-file="https://i0.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-69.png?fit=833%2C164&ssl=1" data-recalc-dims="1" /><figcaption></figcaption></figure><p>In this case, if you want to provide a way for users to lookup Operating Hours, you could use the official Lookup component and reference this field. However, this field is actually part of the Account object. So the configuration of this field would be:</p><figure class="wp-block-image size-large is-resized"><img class="wp-image-15575" src="https://i1.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-70.png?resize=541%2C214&ssl=1" alt="" width="541" height="214" data-attachment-id="15575" data-permalink="https://unofficialsf.com/?attachment_id=15575" data-orig-file="https://i2.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-70.png?fit=707%2C280&ssl=1" data-orig-size="707,280" data-comments-opened="1" data-image-meta="{"aperture":"0","credit":"","camera":"","caption":"","created_timestamp":"0","copyright":"","focal_length":"0","iso":"0","shutter_speed":"0","title":"","orientation":"0"}" data-image-title="image-70" data-image-description="" data-medium-file="https://i2.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-70.png?fit=300%2C119&ssl=1" data-large-file="https://i2.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-70.png?fit=707%2C280&ssl=1" data-recalc-dims="1" /></figure><p>The built-in Lookup Component requires that you specify an existing Lookup field (along with the field’s object). This can require some indirection. For example, if you want to provide lookups to Accounts, you need to find an Account Lookup field on a <span style="text-decoration: underline">different</span> object. </p><p>Fields like OwnerId that can point to more than one object (these are what Salesforce means by ‘polymorphic’ fields) can’t be directly referenced via the built-in Lookup component. Instead of using the Owner field, choose another field which can only be a User, such as CreatedById.</p><h4>Useful Resources about the Official Lookup Component</h4><p><a href="http://SFDC Learn & Share" data-wplink-url-error="true">SFDC Video Introduction</a></p><p><a href="https://unofficialsf.com/learn-about-the-lookup-component-by-jen-lee/">https://unofficialsf.com/learn-about-the-lookup-component-by-jen-lee/</a></p><h2>The Unofficial Lookup Component</h2><p>There’s also a <a href="https://unofficialsf.com/lookup/">powerful but unofficial Lookup component </a>maintained here at UnofficialSF:</p><figure class="wp-block-image size-large is-resized"><img class="wp-image-15586" src="https://i2.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-71.png?resize=368%2C496&ssl=1" alt="" width="368" height="496" data-attachment-id="15586" data-permalink="https://unofficialsf.com/?attachment_id=15586" data-orig-file="https://i2.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-71.png?fit=483%2C650&ssl=1" data-orig-size="483,650" data-comments-opened="1" data-image-meta="{"aperture":"0","credit":"","camera":"","caption":"","created_timestamp":"0","copyright":"","focal_length":"0","iso":"0","shutter_speed":"0","title":"","orientation":"0"}" data-image-title="image-71" data-image-description="" data-medium-file="https://i2.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-71.png?fit=223%2C300&ssl=1" data-large-file="https://i2.wp.com/unofficialsf.com/wp-content/uploads/2019/12/image-71.png?fit=483%2C650&ssl=1" data-recalc-dims="1" /></figure><p>This Lookup component does not attempt to leverage fields of type Picklist. It simply takes an object name and retrieves the appropriate records.</p><p>The Unofficial Lookup Component offers filtering features.</p><p>makes use of direct access.</p><hr /><p><a href="https://unofficialsf.com/the-salesforce-automation-and-decisioning-wiki/about-this-wiki/">About This Wiki</a><br /><a href="https://unofficialsf.com/the-salesforce-automation-and-decisioning-wiki/submission-guidelines/">Contribute to this page!</a></p><div id="like-post-wrapper-154636826-14346-5db5e9bcbbbbb" class="sharedaddy sd-block sd-like jetpack-likes-widget-wrapper jetpack-likes-widget-unloaded" data-src="https://widgets.wp.com/likes/#blog_id=154636826&post_id=14346&origin=unofficialsf.com&obj_id=154636826-14346-5db5e9bcbbbbb" data-name="like-post-frame-154636826-14346-5db5e9bcbbbbb"> </div>
|
