Skip to main content

Search Solution Basics



When is it a good time to create a customized search solution?

  • You're developing an external knowledge base for user support.
  • You're in the mood for a fun Friday night.
  • The sales reps just started using the Sales Cloud in Lightning Experience.
  • You want to put your company branding in the search bar.


What differentiates SOSL from SOQL?

  • Syntax
  • SOSL searches the search index instead of the org database.
  • SOSL searches more efficiently when you don't know in which object the data resides.
  • All of the above.


SOSL works with:

  • REST only
  • SOAP only
  • REST, SOAP, and Apex
  • SOQL only


What does a search for a single object look like in SOSL?

  • FIND {cloud} RETURNING Account
  • FIND in ACCOUNT RETURNING "cloud"
  • FIND "cloud" in ACCOUNT
  • FIND (cloud) RIGHT NOW!


What does a search for multiple objects look like in SOSL?

  • FIND {sneakers} RETURNING ALL ARTICLES
  • FIND {sneakers} in ALL OBJECTS
  • FIND {sneakers} RETURNING Product2, ContentVersion, FeedItem
  • FIND {sneakers} RETURNING Account


How does a custom object search differ from other queries?

  • The name is in all caps.
  • It includes __c at the end of the object name.
  • In the query, you specify that an object is custom.
  • You surround the custom object name in quotes.


How do you create efficient text searches?

  • Limit what you're searching through and limit the number of results.
  • Shorten the search string.
  • Use SOSL and REST.
  • Only search the name field of records.


Which REST resource adds auto-suggest functionality.

  • Auto Suggested Records
  • Search Suggested Article Title Matches
  • RETURNING FieldSpec
  • search()


What can admins do to influence the search results ranking?

  • Host webinars for users on best search practices.
  • Rename records.
  • Set up synonym groups and promoted search terms.
  • Nothing. You're all alone in your quest to improve search solutions.







Comments

Popular posts from this blog

Process Builder is not fired when field update is called from Approval Process

Scenario In Final Approvals section ; in Approval Process we have field update to update Status field. In Process Builder , we have some action that need to be done when Status field is updated in Approval Process.However this process builder is not fired. Solution To handle this, in Field Update in Approval Process , check Re-evaluated Workflow Rules after Field Change as picture below. What happen if field updated from Approval Process. Workflow - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Process Builder - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Trigger - will fire if conditions are matched This is explained in article here  . Field Updates That Re-evaluate Workflow Rules If  Re-evaluate Workflow Rules After Field Change  is enabled for a field update action, Salesforce  re-evaluates all workflow rules on the object if the field update results in a change to the value of the fi

Tips and Tricks : Test class for Invocable method

Issue : I got 100% coverage in my sandbox but when run validation for deployment it returns 0% coverage It turn out that in my sandbox, I am depending on Process Builder to Invocable Apex class, as long I manipulate test data that fire Process Builder it will call Invocable class. This is not useful when deploying it to Production although it gets deployed together with Process Builder. The correct way is to direct call Invocable method inside test class itself. Example of class : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 global class MyCustomObject_StatusUpdate_Util { @InvocableMethod ( label = ' Update Quote Status ' ) public static void updateQuote ( Request [] requests ) { Set < Id > setOppId = new Set < Id >(); List < SBQQ__Quote__c > listQuoteToUpdate = new List < SBQQ__Quote__c >(); for ( Request request : requests ) {