Skip to main content

Latest Post

Record Types & Page Layout Strategy

  Record Types & Page Layout Strategy 💬 In plain words:   Record Types let one object act like different forms for different teams. Different picklist values, page layouts, and processes — same Account object. Use them for truly different business processes. Not for cosmetic layout changes. 📌 Example:   One Account object, two businesses: 'Retail Customer' record type shows B2C picklist values and layout. 'Enterprise Client' shows contract fields and a different sales process. Same table, two costumes. 🧠 One object, many costumes:   A Record Type is a costume on the same object — different picklists and layouts, same table underneath. Concept Record Types split one object into business variants. •   Each type can carry its own subset of picklist values, its own business process — Lead, Case and Opportunity stages — and its own page layout per profile. •   Lightning has changed the calculus. Dynamic Forms and conditional comp...

SOSL Using LWC: Supercharge Your Search in Salesforce

Introduction:

Welcome to our blog on SOSL (Salesforce Object Search Language) using LWC (Lightning Web Components). In this article, we'll explore how you can leverage SOSL within Lightning Web Components to enhance your Salesforce search capabilities. SOSL is a powerful tool for performing text-based searches across multiple Salesforce objects simultaneously, while LWC provides a modern and efficient way to build Lightning components. By combining these technologies, we can create lightning-fast and user-friendly search functionalities. Let's dive in!


## Prerequisites:


To follow along with the examples in this blog, you'll need the following:

  1. Basic understanding of Salesforce development.
  2. Salesforce Developer Edition or a sandbox with the necessary permissions to create Lightning Web Components and Apex classes.
  3. Familiarity with JavaScript, HTML, and CSS.
  4. Salesforce CLI (Command Line Interface) installed and configured.


## Step 1: Setting up the Project


Let's start by creating a new Lightning Web Component to handle our SOSL search functionality. Open your terminal or command prompt and use the following commands:


# Create a new LWC

sfdx force:lightning:component:create -n SoslSearch -d force-app/main/default/lwc


## Step 2: Implementing the SOSL Search


Now, let's edit the soslSearch file to build our UI:


<template>

  <lightning-card title="SOSL Search" icon-name="standard:search">

    <div class="slds-m-around_medium">

      <lightning-input type="text" label="Search" value={searchTerm} onchange={handleInputChange}></lightning-input>

      <lightning-button label="Search" variant="brand" onclick={handleSearch}></lightning-button>

    </div>

    <template if:true={searchResults}>

      <ul class="slds-list_dotted">

        <template for:each={searchResults} for:item="result">

          <li key={result.Id}>

            <a href={getRecordUrl(result.Id)}>{result.Name}</a>

          </li>

        </template>

      </ul>

    </template>

  </lightning-card>

</template>


## Step 3: Writing the JavaScript Controller


Now, let's handle the search functionality in the soslSearch controller:


import { LightningElement, track, api } from 'lwc';

import searchAccounts from '@salesforce/apex/SearchController.searchAccounts';


export default class SoslSearch extends LightningElement {

  @track searchTerm = '';

  @track searchResults;


  handleInputChange(event) {

    this.searchTerm = event.target.value;

  }


  handleSearch() {

    if (this.searchTerm.length >= 3) {

      searchAccounts({ searchTerm: this.searchTerm })

        .then(result => {

          this.searchResults = result;

        })

        .catch(error => {

          console.error('Error executing SOSL query: ', error);

        });

    }

  }


  getRecordUrl(recordId) {

    return `/${recordId}`;

  }

}


## Step 4: Creating the Apex Class


We'll now create the Apex class to handle the SOSL query. Create a new Apex class named SearchController:


public with sharing class SearchController {

  @AuraEnabled(cacheable=true)

  public static List<SObject> searchAccounts(String searchTerm) {

    String soslQuery = 'FIND \'' + String.escapeSingleQuotes(searchTerm) + '\' IN ALL FIELDS RETURNING Account(Id, Name)';

    return search.query(soslQuery);

  }

}


## Step 5: Deploying the Component


To see our SOSL search component in action, we need to deploy it to a Salesforce org. Use the following commands to deploy the component:


# Deploy the component

sfdx force:source:deploy -p force-app/main/default/lwc/SoslSearch


Conclusion:


Congratulations! You've successfully built a lightning-fast SOSL search functionality using Lightning Web Components and SOSL. By harnessing the power of SOSL, you can perform text-based searches across multiple Salesforce objects simultaneously, while the Lightning Web Component provides an intuitive and modern user interface. This combination allows you to deliver efficient and user-friendly search experiences to your Salesforce users.


Happy coding!

Popular Posts

Salesforce LWC Code for Multi-Select Lookup

Introduction: In Salesforce Lightning Web Components (LWC), implementing a multi-select lookup field can enhance the user experience and provide greater flexibility for selecting multiple related records. In this blog post, we will walk through the process of creating a multi-select lookup field using LWC. We will cover the required code snippets and provide step-by-step instructions to help you implement this functionality in your Salesforce org.