#TrailblazerCommunity183 discussing

Good afternoon everyone, hope you are doing well. 

I would like to ask a few questions regarding sandboxes in MARKETING CLOUD NEXT, which came up as I started on a new project. To give you some general context, this client basically wants to do all the development in the sandbox, and once everything is validated and tested, deploy it to production—which is totally fine.

However, here are my questions: 

1 - Regarding WhatsApp: Can I perform the setup configuration, warming, and testing all within the sandbox? My concern is whether I will need to replicate this entire process in production later on. If there is an ideal scenario or best practice, I would like to understand how to proceed with this step. 

2 - Regarding Email: Similar to the WhatsApp situation, my main question is about the domain/subdomain in the sandbox. When doing all this setup, do I need to perform the IP/domain warming normally? Is it necessary to create a domain/subdomain to work in the sandbox as well, and then repeat the same step for production? Or is the process different for a sandbox? 

In short, these are my main questions, but just to reiterate: this client wants everything to be developed and tested in the sandbox, and we will only deploy to production once everything is validated.

Because of this, I have these questions so I can understand the best way to move forward. 

Thank you. 

As a Technical Architect in Salesforce Services, I get a front-row seat to what's actually possible with agents, before most of it becomes mainstream. 

The biggest shift I'm seeing:

Instead of just surfacing information, they're taking action: updating records, triaging requests, and kicking off processes. That frees people to focus on judgment calls and relationships instead of repetitive steps. 

Working across customer projects, a few patterns keep showing up:

• Start with a narrow, high-value use case. The wins come from agents that do one job well, not ones that try to do everything.
• Data quality is the foundation. An agent is only as good as the data and context behind it, so grounding it in trusted data matters as much as the prompt.
• Guardrails build trust. Clear boundaries and human handoffs help teams adopt agents with confidence.

The most exciting part is how quickly customers go from "what if?" to "it's live." What used to take months of custom build now comes together in weeks. 

I'd love to hear from others:

Cue the confetti, Trailblazers! Together, you’ve officially earned 1.5 million Salesforce certifications across the ecosystem! 🎉

Congratulations to each and every one of you on investing in yourselves to achieve such an incredible milestone! 🥳 We’re honored you chose to learn, earn, and grow with us.

Ready for what’s next? Explore certifications today: https://sfdc.co/salesforce-certifications 

@* Trailhead Official * @* Trailhead Academy * @Salesforce Certified Professionals @Trailblazer Community Cove @* Salesforce Administrators * @* Salesforce Developers * @Architect Trailblazers @Salesforce Business Analysts @Consultant Trailblazers #Salesforce #Certifications #Trailhead #TrailblazerCommunity #Agentforce #Salesforce Admin #Salesforce Developer

Salesforce Developer Roadmap in the AI Era (2026–2027) 

Hi Trailblazers, 

With Agentforce, Data 360, and AI becoming part of Salesforce development, I believe developers need to strengthen their core technical skills while learning new AI capabilities.

Here is my suggested learning roadmap for beginners and working professionals. 

1. Salesforce Fundamentals

• CRM basics, Objects, Fields, and Relationships
• Security, OWD, Profiles, and Permission Sets
• Flow Builder and Validation Rules

Salesforce Developer Beginner

• SOQL, SOSL, and Relationship Queries
• Apex Classes, Triggers, and Collections
• Bulkification, Governor Limits, and Test Classes

Apex Basics

• HTML, CSS, and JavaScript
• Components, Events, and Data Binding
• LWC with Apex and Lightning Data Service

LWC Developer Guide

• REST APIs, JSON, and OAuth 2.0
• Named Credentials and Apex Callouts
• Platform Events and Asynchronous Apex

Apex Integration Services

• VS Code, Salesforce CLI, and Git
• Sandboxes, Deployments, and Testing
• CI/CD and DevOps Center

Salesforce CLI

• Agentforce Builder, Subagents, and Actions
• Agent Script and Prompt Builder
• Apex and Flow Actions for AI Agents
• Agent Testing, Security, and Debugging

Agentforce Developer Guide

• Data Streams and Data Lake Objects
• Data Mapping and Identity Resolution
• Data Graphs, Retrieval, and Agentforce Grounding

Data 360 Learning

Data 360 Overview – SFDCINDIA

Build at least three practical projects:

1. Student Management System – Admin, Apex, and LWC
2. Customer Support Application – Flow, Integration, and Security
3. AI Customer Support Agent – Agentforce, Actions, and Data 360

My Suggestion:

Don't jump directly into Agentforce without understanding Salesforce fundamentals.

Learn Salesforce → SOQL → Apex → LWC → Integration → DevOps → Agentforce → Data 360

AI can help developers write code faster, but understanding business requirements, architecture, security, debugging, and testing will remain essential.

My Key Point: The future belongs to developers who understand both Salesforce Development and AI.

What skills are you focusing on to stay relevant in the AI era? 

Venkat Yadav | SFDCINDIA

#Salesforce Developer #Salesforce Admin #Agentforce #Data Cloud #TrailblazerCommunity #Trailhead Challenges