* Salesforce Administrators *

⛰️🛡️ New Hands-on Workshop for Premier & Signature Developers: Secure the Code: Find and Fix Vulnerabilities (DEX003) 

Insecure custom code is one of the leading causes of data breaches. In this 90-minute instructor-led workshop, you'll step into the role of a security-focused developer to audit and remediate critical vulnerabilities in Lightning components and Apex classes through a series of challenges.  

This hands-on workshop teaches developers how to prevent script injection, encrypt data securely, manage secrets, and control record access. You'll also learn to identify authentication flaws and data exposure risks. this practical workshop is for developers working with custom code at any stage: 

• Build new code — learn to bake in secure patterns from the start, so vulnerabilities never make it to production
• Review existing code — sharpen your eye for spotting injection flaws, insecure data handling, and access control gaps in code you didn't write
• Maintain and harden production orgs — Use the Developer Console or VS Code to apply Salesforce platform security best practices that protect applications from evolving threats

Sessions are live and available! :calendar:

• Wed Sep 2 — 3:30pm CET/Paris
• Tues Sep 8 — 3:30pm ET/New York
• Mon Sep 21 — 9am IST/Kolkata
• Mon Oct 19 — 9am ET/New York
• Check the session listings for additional workshops across regions :tada:

Interested in the Admin version of this security workshop? Check out upcoming sessions for ADX012

👉 Premier and Signature customers — Register today on Trailhead Academy — Course code: DEX003

#Salesforce Developer #Slack Developers

I implemented a Salesforce automation to simplify how we handle duplicate Prospect and Customer Accounts. Sharing the approach in case it helps other Salesforce Admins facing a similar scenario.

🔹 The Business Problem

In our process:

• Sellers manually create Prospect Accounts in Salesforce.
• Once a prospect becomes a customer, the Customer Account is automatically created in Salesforce through an integration with another system.
• The original Prospect Account remains in Salesforce.
• This can result in a Prospect Account and Customer Account representing the same company i.e, duplicate accounts.

Previously, sellers had to identify these duplicates and submit a ticket manually so an Admin could merge the records.

🔹 The Solution

I built an automation that follows this process:

Duplicate identified → Prospect Account flagged → Duplicate Account button + bell notification displayed → Seller clicks the button → Email sent to Service/Admin team → Admin reviews and merges the accounts

🔹 Implementation Steps

1. Create the Matching Rule and Duplicate Rule : A Matching Rule and Duplicate Rule to identify a Prospect Account and Customer Account as duplicates based on our internally defined matching criteria.

2. Create a Record-Triggered Flow: Record-Triggered Flow that runs when a Duplicate Record Set is created or updated.

Within the Flow:

• Get Duplicate Record Items: Retrieve the Duplicate Record Items associated with the Duplicate Record Set.
• Loop Through Duplicate Record Items: Loop through the Duplicate Record Items and assign the relevant Account/Company Name to a Flow variable.
• Find the Matching Account: After the loop, use Get Records on the Account object to find the corresponding Account based on the Account/Company Name stored in the Flow variable.
• Flag the Prospect Account: When the matching Account is found, update the Prospect Account and set our custom Duplicate Account checkbox field to True.

3. Display the Duplicate Account Button + Bell Notification: Duplicate Account button/action to the Account Lightning Record Page and configured Conditional Visibility based on the Duplicate Account checkbox.

When the checkbox is set to True, the seller sees the Duplicate Account button along with a bell notification. This gives the seller an immediate indication that Salesforce has identified the Account as a duplicate and that the records need to be reviewed/merged.

4. Notify the Admin Team: When the seller clicks the Duplicate Account button, an email is automatically sent to our ticketing system and Admin reviews and merges both Prospect and Customer accounts.

Here are screenshots of the flow:  

  #Salesforce Admin #Flow #Sales Cloud

Hi! I’m trying to convert a social account so that I can enable the Activate User option for its contacts, allowing them to use the Experience site.

However, when I click the standard Activate Account button for the contact, I get this error banner (shown in the screenshot), and I’m not sure why.

My user has admin permissions and the highest-level role. Has anyone else encountered this error or knows what might be causing it? 

🎉 Big shoutout to our incredible Forum Ambassador, @Manoj Nambirajan for an awesome deep dive on "Send Opportunity Notification for Specific Stage Movements"!📘 Check out the article here >> https://help.salesforce.com/s/articleView?id=005393369&type=1 

🔍 Found it helpful? Have thoughts to share?

 Let us know by clicking the "Yes" or "No"  button at the bottom of the article—your feedback helps us improve!> 🔍 Found it helpful?" style="display: block;" /> #Flow

As we race toward Dreamforce Trailblazer Bootcamp on September 12-14, lace up every Tuesday, Wednesday, and Thursday for #TrailblazerTrackMeets, where we’re sharing details about each of our bootcamp tracks and the instructors teaching them! 👟

We’re off to a running start with the Agentforce Service Specialist track, where instructor Alok Agarwal will guide students through building, customizing, and deploying AI-powered service agents from scratch. Don’t get left in the dust! 💨

On your marks, get set… register: https://sfdc.co/DF26TrailblazerBootcamp

@* Trailhead Official * @* Trailhead Academy * @Trailblazer Community Cove @* Salesforce Developers * @* Salesforce Administrators * #Salesforce #Certifications #Trailhead #TrailblazerCommunity #Salesforce Developer #Salesforce Admin #AwesomeAdmins #Agentforce