Feed

Hi there! 

Please check your permission set name correctly sometime you miss spilling and also read the trailhead guide carefully you have not giving the permission which is required to complete the challenge go step -> permission set -> check you gave correct read & write permission to individual field!

Wondering how to convert your large OST files without Outlook? Try the MailConverterTools OST File Converter. Using this top-notch utility, users can convert OST files to MSG, PST, OLM, PDF, MBOX, and many other formats. What’s more, you can migrate your OST data directly to Gmail, iCloud, Thunderbird, Office 365, and other platforms. The tool preserves folder hierarchy and attachments, which is perfect for safe backup or transfers. Apart from this, the software introduces the Naming Convention Feature, using which users can rename the resultant folder according to their preference.

Hi there! 

Since direct permission changes aren't allowed,  

• you'll need to create two brand new fields on the Job Application object. Give these new fields names like "Position" and "Candidate," ensuring their data types are suitable (e.g., lookup fields to the Position and Candidate objects). 

• Once created, you can then grant the correct read and edit permissions to these new fields within your "Manage Job Applications" permission set. 

• Finally, update your page layouts or any automations to use these new fields.

Hi,

thanks for sharing this, I’m also while working on a Campaign flow.

Just like you, I’ve:

• Tried rebuilding the flow from scratch many times → same error

I keep getting the "We can’t refresh your data stream" error.

Did you happen to find a fix or workaround? Any insights or debugging tips you discovered would be greatly appreciated!

Thanks in advance, 

Giovanni

Hello @Tejas Padol, 

So let's start... Before we start, make sure you have:

1. Salesforce CLI installed on your computer.
2. VS Code set up with the Salesforce Extension Pack.
3. A Salesforce project (SFDX) open in VS Code.
4. You’re logged into your org (sfdx force:auth:web:login).
5. Debug Logs are enabled for your user.

Now, once all is set. 

Step 1: Run your code to generate a log

First, trigger the code that you want to debug. 

 You can do this by:

• Running a test class
• Executing anonymous Apex
• Doing an action in the UI (like creating a record that fires a trigger)

This will create a debug log in your org. 

Step 2: Download the log into VS Code

In the VS Code terminal, run: 

sfdx force:apex:log:get --number 1 

This pulls the latest log file into the logs/ folder of your project. 

Step 3: Open the log with Replay Debugger

In VS Code:

• Open the .log file from the logs folder.
• Right-click and choose “Start Debugging”  
   OR  
   Press F5 while the log file is open.

This starts the Apex Replay Debugger session. 

Step 4: Set breakpoints in your Apex code

Open the Apex class (or trigger) you're trying to debug.

Click on the left side of the line number to set a breakpoint — this is where the debugger will pause so you can check what’s going on. 

Step 5: Use the debugger tools

At the top, you’ll see familiar buttons like: Continue, Step Over, Step Into, Step Out, and Stop. 

Step 6: Find the issue

As you step through, look for:

• Any unexpected null values
• Logic not being executed
• Incorrect calculations
• Or anything that doesn’t behave as expected

Step 7: Re-test and debug again 

NOTE - Add System.debug() statements in your code. 

I hope that helps. 

Thanks and regards 

Amit Kumar

Configuring a custom domain for your Salesforce Experience Cloud (LWR) site with Salesforce CDN involves two main steps: first, adding your domain in Salesforce Setup, where you'll receive a CNAME target. Second, you'll create a CNAME record in your DNS provider (like AWS Route 53) pointing your custom domain to this Salesforce-provided target. Finally, you'll set up a custom URL in Salesforce to link your domain to your specific Experience Cloud site. Sandboxes work similarly for validation, just ensure you select the correct associated org during the domain setup in Salesforce. The key is precise CNAME entry and allowing for DNS propagation time.