I need to exclude:
opportunities from updating when Account owner changes using standard change owner wizard and retain the old owner of the opportunity record. In trigger I tried to capture before change owners and tried to update after changes with the old owners but the splits are not added with new owner and when my logic runs it throws an error atleast one revenu split must be with owner. How to overcome this as flows and triggers are cascaded by the standard functionality.Thanks!
#Salesforce Developer #Apex #Triggers #Flows #TrailblazerCommunity #Salesforce
@Abhishek R I tried that way it is bypassing flow and triggers.I am trying to use CDC to capture the changed owner not sure will that work.Thanks for the reply.
Challenge Not yet complete... here's what's wrong:
At least one unit test from
RewardsCalloutServiceTest has failed during the most recent test run. Make sure to run all unit tests and they all pass. (module: apex callouts)
#Trailhead Challenges #Trailhead #Salesforce Admin #Salesforce #Apex #Salesforce Developer
++ You can try the code below,
@isTest
public class RewardsCalloutServiceTest {
@isTest static void testSubmitUsersForRewardCallout() {
Test.setMock(HttpCalloutMock.class, new RewardsCalloutServiceMock());
// Create test data for Wellness Journey
List<Wellness_Journey__c> journeys = new List<Wellness_Journey__c>();
User testUser = [SELECT Id, Name, Username, Email FROM User WHERE Id = :UserInfo.getUserId()];
for (Integer i = 0; i < 12; i++) {
Wellness_Journey__c journey = new Wellness_Journey__c(
OwnerId = testUser.Id
);
journeys.add(journey);
}
insert journeys;
Test.startTest();
Database.executeBatch(new WellnessJourneyRewardsBatch());
Test.stopTest();
// Assertions to validate the behavior can be added here
Integer statusCode = RewardsCalloutService.submitUsersForRewardCallout(JSON.serialize(journeys));
System.assertEquals(200, statusCode, 'The HTTP status code should be 200');
}
}
Hi everyone,
This is Shakthi. I'm a developer from India. I have 9 months of experience working on Creatio (a low-code CRM platform) and I’m transitioning into Salesforce Development. Here's my Trailblazer account that I've using on Trailhead to learn things. (https://www.salesforce.com/trailblazer/z9n4nxujjb68i4d63b)
Progress so far:
- Developer Beginner Trail
- Build Lightning Web Components Trail
- Core Apex modules (Triggers, Async, Testing, Integration Services)
- Apex Callouts Superbadge
- Apex Web Services Superbadge
I’ve also covered basic SLDS.
Currently going through one of Coding With The Force YT playlist for Apex beginners.
My questions on the next steps in my transition journey:
1. What should I focus on next?
- More Superbadges?
- Start preparing for any certifications, if yes which ones are relevant to the industry today for transitioning developers?
- Or something else?
2. Any roadmap suggestions for someone transitioning from another low-code platform into Salesforce Development?
Any advice would be really appreciated. Thank you!
P.S: I have been using AI to guide myself in learning Salesforce development and in writing this very message. Wanted to mention it right off the bat.
Thank you all in advance for all the guidance and support.
#Salesforce Developer #Certifications #Trailhead #Trailblazer #Apex
Hi everyone,
If you are testing your agents locally using Agentforce DX / Vibes and hitting a generic "Something went wrong" error pointing to missing permission sets (like AgentforceServiceAgentBase or EinsteinGPTPromptTemplateUser) during live test execution, check your sub-agents.
The Issue: This often happens due to an unpopulated reference in the agent script under Local Events. The Fix: Look at your Check Events action under your local sub-agent. If the Reference action type is blank, manually select or set it as a Prompt Template. You can right-click the script and run AFDX: Validate This Agent to verify your structure before starting the simulation server again.
Hope this saves some troubleshooting time!
#Agentforce #VSCODE #Apex
If you’re testing locally with Agentforce DX / Vibes and get a generic “Something went wrong”
error mentioning missing permission sets like AgentforceServiceAgentBase or EinsteinGPTPromptTemplateUser, don’t only check permissions.
In some cases, the real issue is an unpopulated reference in the agent script.
Go to your Local Events sub-agent and check the Check Events action. If the Reference action type is blank, set it to Prompt Template.
Then right-click the agent script and run
AFDX: Validate This Agent before restarting the simulation server.Hi Everyone,
I am trying to implement WhatsApp messaging through Salesforce Sales Engagement Cadences using WATI API integration, but I am facing issues with Cadence Step Flow execution and variable passing.
Current Architecture:
Contact Record Triggered Flow
→ Add Contact to Cadence
→ Cadence Step Flow
→ Apex Invocable Action
→ Queueable Apex
→ WATI API Callout
My goal:
When a contact reaches a cadence step, I want to automatically send a WhatsApp template message through WATI.
What I have implemented:
Current Flow Payload:
959585****|||abd|||{"name":"Rakesh"}
Invocable Apex:
public with sharing class WatiWhatsAppService {
public class Request { @InvocableVariable(required=true) public String rawInput; } @InvocableMethod( label='Send WATI WhatsApp Message' description='Cadence-compatible WhatsApp action.' ) public static void sendWA(List<Request> requests) { List<String> rawInputs = new List<String>(); for(Request req : requests){ if(String.isNotBlank(req.rawInput)){ rawInputs.add(req.rawInput); } } System.enqueueJob(new WatiQueueable(rawInputs)); }
}
Issue:
Questions:
Any guidance or recommended architecture would be very helpful.
Thanks!
VS Code + Git diff is probably the most common approach for Apex code comparison.
For larger orgs or multiple sandboxes, teams also use org-to-org metadata comparison tools to compare:
We used to compare retrieved metadata manually, but recently started using BOFC for quicker sandbox vs production Apex comparisons:
https://bofc.io/how-to-compare-apex-classes-across-multiple-salesforce-orgs/
Best practice is definitely keeping Git as the source of truth and validating differences before every deployment.
