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...

Unveiling the Power of Named Credentials in Salesforce with Comprehensive Code Examples

Introduction:


Named Credentials are a powerful feature in Salesforce that allow you to securely authenticate and connect to external services and APIs without exposing sensitive information like usernames and passwords. In this blog post, we'll delve into the world of Named Credentials, understand their significance, and provide you with in-depth code examples to illustrate their implementation in various scenarios.


Table of Contents


1. What are Named Credentials?

2. Advantages of Using Named Credentials

3. Creating Named Credentials in Salesforce

4. Code Examples:

   a. Authenticating with an HTTP Endpoint

   b. Integrating with a REST API

   c. Connecting to a Salesforce Org

   d. Handling Custom Authentication

5. Best Practices

6. Conclusion


1. What are Named Credentials?


Named Credentials are a way to define an endpoint and its associated authentication information in a single location in Salesforce. They act as a central hub for securely storing authentication details such as usernames, passwords, tokens, and certificates. Named Credentials provide a seamless and secure way to connect to external services, reducing the risk of exposing sensitive data.


2. Advantages of Using Named Credentials

  1. Enhanced Security: Named Credentials shield sensitive authentication information from being hardcoded in your code.
  2. Centralized Management: Manage authentication details in one place, simplifying maintenance.
  3. Encrypted Credentials: Passwords and tokens are encrypted, providing an extra layer of security.
  4. Simplified Authentication: Easily switch between authentication methods without modifying your code.

3. Creating Named Credentials in Salesforce

  1. Navigate to "Setup" > "Named Credentials."
  2. Click on "New Named Credential."
  3. Fill in the required details, including the URL, label, and authentication settings.
  4. Choose an appropriate authentication type, such as Password Authentication, OAuth 2.0, or Certificate.
  5. Save the Named Credential.

4. Code Examples


a. Authenticating with an HTTP Endpoint


HttpRequest req = new HttpRequest();

req.setEndpoint('callout:My_Named_Credential/services/data/v53.0/query?q=SELECT+Id+FROM+Account');

req.setMethod('GET');


Http http = new Http();

HttpResponse res = http.send(req);

System.debug(res.getBody());


b. Integrating with a REST API


HttpRequest req = new HttpRequest();

req.setEndpoint('callout:My_Named_Credential/restApiEndpoint');

req.setMethod('POST');

req.setHeader('Content-Type', 'application/json');

req.setBody('{"key": "value"}');


Http http = new Http();

HttpResponse res = http.send(req);

System.debug(res.getBody());


c. Connecting to a Salesforce Org


HttpRequest req = new HttpRequest();

req.setEndpoint('callout:My_Named_Credential/services/apexrest/MyRestService');

req.setMethod('GET');


Http http = new Http();

HttpResponse res = http.send(req);

System.debug(res.getBody());


d. Handling Custom Authentication


HttpRequest req = new HttpRequest();

req.setEndpoint('callout:My_Named_Credential/oauth2/token');

req.setMethod('POST');

req.setHeader('Content-Type', 'application/x-www-form-urlencoded');

req.setBody('grant_type=password&client_id=myClientId&client_secret=myClientSecret&username=myUsername&password=myPassword');


Http http = new Http();

HttpResponse res = http.send(req);

System.debug(res.getBody());


5. Best Practices

  1. Avoid hardcoding sensitive information in your code.
  2. Leverage Named Credentials for all external service integrations.
  3. Regularly review and update Named Credential settings as needed.
  4. Follow the principle of least privilege when configuring authentication settings.

6. Conclusion


Named Credentials are a game-changer when it comes to securely integrating Salesforce with external services and APIs. By centralizing authentication details and following best practices, you can ensure a robust and secure connection between your Salesforce instance and various external resources. The comprehensive code examples provided in this blog post should equip you with the knowledge and confidence to leverage Named Credentials effectively in your Salesforce development projects.

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.