#Lookup Filter0 discussing

So I have this custom object called Candidate__c, and there is this lookup field called Service_Coordinator__c that looks up to Contact. This lookup field has a lookup filter that is dependent on another field in Candidate, a picklist field called Regional Center. The lookup field should show only the Contacts when they are affiliated with an Account with the same name as the Candidate Regional Center. The lookup field works the way I want when I edit it directly on the record page, but how should I make the lookup field work that way when it is referenced in a Screen Flow or an Experience Builder page?

#Lookup Filter

Hi All,

 When we create task on any object inside salesforce, the assign to id  lookup field shows salesforce licence users along with community users. How can we apply filters on task object assign to field so that it doesn't show community users. I want only the salesfoce users to come up in the look up field.

I also tried to explore filters on lookup field. But lookup filters is not available on assign to field on task.

Any suggestion on how to achieve this?

Thanks,

Adarsh  

Error messages can originate from a variety of sources in our org (Validation Rules, Lookup Filter, and even code).

Finding their origin can sometimes be difficult and time-consuming. Similarly, email templates can also be hard to locate.

Luckily, there is a simple way of locating them 🙂

A faster way to identify the Source of Validation Rules, Lookup Filters, and Email Templates

@Alex Edelstein 

1. We have a process that executes after a Case is updated.  It's purpose is to update the Case's Contact record.
2. The Contact object's Account field has a Lookup Filter.  The filter was added AFTER some records were created with values that would now fail with the current filter.
3. The Case record is updated, executing the Process.
4. The Process attempts to update a custom field on the Case's parent Contact.
5. The Process fails with the error:   FIELD_FILTER_VALIDATION_EXCEPTION .
6. If the Contact record is corrected or if the Lookup Filter is altered then the Process works as expected.
7. Is there a method to bulletproof the process to avoid the user seeing the Fault Error Message?
8. With Flow we have fault handling.  I am hoping I could update the Contact via the Flow, and if it should fail due to the same error, the fault handling would handle it better such as executing a Core Action.
9. My question is if the Process calls the Flow, and then Flow's Fault Handler executes, would the Process still generate the same error to the end-user?
10. Or do you have any other suggestions?

@Salesforce Process Builder @Jennifer (Jen) Lee @RAKESH GUPTA @Meighan Brodkey @Jake Faris @Shannon Hale

@Elna Miller @Jacinta Burke Is Salesforce aware of this "Idea", just curious as this seems like the sort of thing that shouldn't be an Idea when (to me) it is clearly a bug.  In short, you set a lookup filter as optional, in Classic the user is able to select not to observe the filter and search outside of the parameter.  In Lightning, the user is not given a choice to override the filter and is not even aware that a filter is in operation.

Lightning Lookup Filter Fix