Skip to main content
Temas#TrailblazerCommunity

#TrailblazerCommunity175 debatiendo

Formular una pregunta...
Sahil Gupta (Software Developer en Quarks) publicó en #Trailhead
2 oct, 10:51

Hi Trailblazer Community,

I attended Dreamforce 2026 live on Salesforce+ and watched the live sessions during the event. I also used the same email address associated with my Trailblazer account for the Dreamforce/Salesforce+ registration and attendance.

However, the Dreamforce 2026 stamp is still not showing on my Trailblazer profile.

Has anyone else experienced the same issue? Is there any additional step I need to complete to receive the stamp, or should I wait for the attendance verification to be processed?

Any guidance from the community or Salesforce team would be greatly appreciated.

Thank you! 🙌

#Dreamforce2026 #SalesforcePlus #Salesforce #TrailblazerCommunity #Trailblazer #SalesforceCommunity #Dreamforce #Trailhead

2 comentarios
Escribir un comentario...
0/9000
Venkat Yadav (Founder & Lead Trainer en SFDCINDIA) publicó en #Agentforce
17 oct, 04:46

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

 

2. SOQL & Apex Development

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

Apex Basics

 

3. Lightning Web Components (LWC)

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

LWC Developer Guide

 

4. Salesforce Integrations

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

Apex Integration Services

 

5. Salesforce DevOps

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

Salesforce CLI

 

6. Agentforce & AI Development

  • 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

 

7. Data 360

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

Data 360 Learning

Data 360 Overview – SFDCINDIA

 

8. Real-World Projects

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

1 comentario
Escribir un comentario...
0/9000
Sara Halvorson (PMM en Salesforce) publicó en #Trailhead
21 jul, 15:18

🚀 Agentic AI is evolving — and so are the Agentblazer Status trails. 

 

We've refreshed Champion, Innovator, and Legend with new content to make sure your skills are in step with AI innovation. 

 

Here’s what's new: 

 

⭐️ Champion — 

⭐️⭐️ Innovator —

⭐️⭐️⭐️ Legend —

And now every Agentblazer unit has AI-generated audio so learning AI is accessible from anywhere.

 

Skill up: trailhead.com/agentblazer

 

#Trailhead  #Agentforce  #Salesforce Developer  #Salesforce Admin  #TrailblazerCommunity  #Salesforce  #New Releases

 

🚀 Agentic AI is evolving — and so are the Agentblazer Status trails. We've refreshed Champion, Innovator, and Legend with new content to make sure your skills are in step with AI innovation.

 

 

5 comentarios
  1. Rohit Kumar (Dell Technologies)
    17 oct, 08:44

    Use {{ ref('Account','Id') }} instead of the Trailhead-recommended approach, which was causing an issue. I used this alternative, and it successfully resolved the error. 

    Below the generated JSON.  

    Use {{ ref('Account','Id') }} instead of the Trailhead-recommended approach, which was causing an issue. I used this alternative, and it successfully resolved the error. Below the generated JSON.

     

     

Escribir un comentario...
0/9000
Akshata Sawant (Developer Advocate en Salesforce) publicó en #Salesforce Developer
14 oct, 12:47

With the Headless Experience Layer (HXL), you build one interactive widget in declarative JSON, and it renders natively in Agentforce, Claude, ChatGPT, and Slack. No rebuilding the same screen for every surface. 

 

Ready to try it? Start here:

 

 

#Salesforce Developer  #Salesforce Admin  #Agentforce  #Salesforce  #TrailblazerCommunity

2 comentarios
Escribir un comentario...
0/9000
Sai Pavani Yamsani (Developer en Gurunanak Institute of Technology) preguntó en #Trailhead
16 oct, 16:27
1. What is the best roadmap to learn SOQL, Apex, LWC, and Salesforce integrations effectively?

#Trailhead #TrailblazerCommunity #Apex

 

For a learner with strong Trailhead experience who wants to move into Salesforce development, what is the recommended learning sequence for SOQL, Apex, Lightning Web Components (LWC), and REST API integrations, and what hands-on projects can help build confidence in each area?

1 respuesta
  1. Venkat Yadav (SFDCINDIA)
    17 oct, 04:15

    Hi @Sai Pavani Yamsani Good question! Since you already have strong Trailhead knowledge, I suggest learning Salesforce Development in this order:

    1. SOQL → Apex → LWC → REST API Integration

    • SOQL: Learn SELECT, WHERE, ORDER BY, and relationship queries. Practice fetching Accounts and related Contacts.
    • Apex: Start with classes, methods, collections, DML, triggers, bulkification, and test classes. Build a simple Student Management System.
    • LWC: Learn HTML, JavaScript, data binding, events, and Apex integration. Build a searchable Account List component.
    • REST API: Learn GET, POST, JSON, authentication, Named Credentials, and Apex callouts. Integrate Salesforce with a public API.

    2. Official Learning Resources

    3. My Suggestion

    Build one complete project using all four skills, such as a Student Management Application with SOQL, Apex, LWC, and REST API integration.

    Don't focus only on completing Trailhead badges. Spend more time writing code, debugging errors, and building real-world projects.

    Consistent hands-on practice is the best way to become a confident Salesforce Developer.

    Hope this helps!

    Venkat Yadav | SFDCINDIA

Escribir una respuesta...
0/9000
Manav joshi (developer en RCG Global Services, Inc.) preguntó en #Salesforce Developer
15 oct, 09:24
can we get available fields and metadata api column name mapping for user object

I am currently encountering a similar challenge. I am building a custom Lightning Web Component (LWC) to replicate standard Salesforce List View functionality, which will allow users without administrative access to create and manage their own list views. I am utilizing Named Credentials to handle the creation and updating of these list views.

However, I am running into a few issues:

First, I am unable to retrieve only the fields that are eligible for List View creation. When I fetch the fields for the User object, the system returns every field on the object. I have realized that not all of these fields are actually available or supported for use inside a standard List View.

Second, when attempting to save the list view via the Metadata API, the standard SOQL field API names fail. When I fetch an existing list view to inspect it, the XML returns completely different internal API names, as shown in the snippet below: 

<ListView xmlns="

http://soap.sforce.com/2006/04/metadata

"> 

    <fullName>testing_list_view_2</fullName> 

    <columns>CORE.USERS.FAX</columns> 

    <columns>CORE.USERS.FIRST_NAME</columns> 

    <columns>FULL_NAME</columns> 

    <columns>DVC_Is_Manually_Cleared__c</columns> 

    <columns>CORE.USERS.LAST_LOGIN</columns> 

    <columns>CORE.USERS.LAST_NAME</columns> 

    <columns>CORE.USERS.MIDDLE_NAME</columns> 

    <columns>CORE.USERS.CELL</columns> 

    <columns>CORE.USERS.COMMUNITY_NICKNAME</columns> 

    <columns>OOO_End_Date__c</columns> 

    <columns>OOO_Start_Date_Time__c</columns> 

    <columns>CORE.USERS.PHONE</columns> 

    <columns>Planned_Activation_Date__c</columns> 

    <columns>CORE.USERS.STATE_CODE</columns> 

    <columns>CORE.USERS.SUFFIX</columns> 

    <filterScope>Everything</filterScope> 

    <label>testing list view 2</label> 

    <sharedTo> 

        <allInternalUsers></allInternalUsers> 

    </sharedTo> 

</ListView> 

 

Based on this, I have two questions:

  1. Is there a programmatic way to retrieve only the specific fields that are available for selection when creating a User List View in the standard Salesforce UI?
  2. Is there an official documentation page or mapping matrix I can refer to that translates standard SOQL field API names to these specific Metadata API names?

#Salesforce Developer  #TrailblazerCommunity  #Apex

Escribir una respuesta...
0/9000
kallimulla Abdul Kadhar (Associate Consultant en TATA Consultancy Services) preguntó en #Salesforce Developer
16 oct, 08:51
Wanted to attach image files to Salesfore from Web-to-Case

We have third party site which creates a Web-to-case and we wanted to attach the image files to the case. The site is open to all in internet. So how to attach the image file securely in salesforce. 

 

#Salesforce Developer  #Trailhead Challenges  #TrailblazerCommunity  #Service Cloud

3 respuestas
  1. Asim Ansari (Intellectual Clouds)
    16 oct, 09:25

    Hi @kallimulla Abdul Kadhar, 

    Standard Web-to-Case can’t carry attachments. The form it generates posts plain form fields, not multipart uploads, and it never creates ContentVersion records. The one answer on that thread says the same. Since your site is open to the internet, the safe approach is to keep the file upload off the Salesforce side of the public boundary until the file has been vetted.  

     

    Recommended pattern: your site’s backend handles the upload and calls Salesforce with an authenticated integration user 

    1. Browser → your backend. The site’s own server receives the image. It validates the file before anything reaches Salesforce: 
      • Allow-list of types, checked by magic bytes and not just the extension (JPEG/PNG/WebP/GIF, and no SVG, since SVG can carry script).
      • Hard size limit and a limit on the number of files per case.
      • Malware scan (ClamAV or a cloud scanning service).
      • Bot protection and rate limiting (reCAPTCHA/Turnstile, per-IP throttling).
    2. Backend → Salesforce, authenticated. Don’t use Web-to-Case for this flow. Create the Case through the REST API, using an OAuth Connected App / External Client App (client-credentials or JWT bearer flow) as a dedicated integration user. 
      • The credentials stay on your server and are never exposed in the browser.
      • Give the integration user a minimal permission set: create Case, create ContentVersion, and nothing else.
    3. Attach the file via REST: POST a ContentVersion (base64 body for small files, multipart for larger ones), then a ContentDocumentLink to the Case. Or use the Composite API to create the Case and attach the file in one call.
    4. Case ID handling. Never let the browser pass a Case ID that it supplies. The backend should use the ID returned from its own Case creation.

    Alternatives: 

    An Experience Cloud site with a Case form and the file upload component fits if the site can be replaced or embedded. It’s native to Salesforce, but the Guest User risk is real, so prefer authenticated external users over Guest access.  

     

    An Apex REST endpoint (@RestResource) fits if you need custom validation inside Salesforce. The caller still has to be authenticated, so don’t expose the endpoint to the Guest profile.  

     

    Uploading to S3 or Azure Blob and storing a link on the Case fits high-volume or large-file scenarios. The files then live outside Salesforce, so access control and retention become your responsibility.  

     

    Email-to-Case works if users can email their attachments, but sender verification is weak and attachment limits apply.  

     

    The backend-plus-REST-API approach remains the strongest option on security, but it needs developer work on the third-party site.  

     

    Avoid 

    • Exposing an Apex REST endpoint or Visualforce page to the Guest User profile to accept uploads. Guest access is the most common source of Salesforce data exposure, and an open file-upload path invites abuse and storage exhaustion.
    • Storing credentials in client-side JavaScript.
    • Trusting the filename or content type sent by the client.

    Other points

     

    • Files in Salesforce count against your file storage limits, so size caps matter.
    • Decide whether the images need to be visible to the customer later, since that changes the sharing setup (ContentDocumentLink visibility).
    • Consider async scanning: store the file in a quarantine state until the scan passes, then attach it.

    I hope you find the above information helpful. If it does, please mark it as Best Answer to help others too.

Escribir una respuesta...
0/9000
Venkat Yadav (Founder & Lead Trainer en SFDCINDIA) preguntó en #Agentforce
9 sept, 07:05
Which Salesforce skill do you think will be the most important for professionals in the next 2–3 years: Agentforce, Data 360, Apex/LWC, Integration, or something else? Why?

After many years of working with Salesforce, one change I’m seeing clearly is the shift from traditional CRM automation toward AI-driven, agent-based solutions. 

 

With Agentforce, Data 360, Flow, Apex, and AI agents becoming more connected, I’d love to hear from the Trailblazer Community: 

 

What Salesforce skill do you believe will be the most important for professionals over the next 2–3 years — Agentforce, Data 360, Apex/LWC, Integration, or something else? 

 

And more importantly, why? 

 

Looking forward to learning from your experiences and perspectives.  

 

#Salesforce #TrailblazerCommunity #Agentforce #Data360 #Salesforce_developer #Salesforceadmins

4 respuestas
  1. Venkat Yadav (SFDCINDIA)
    16 oct, 07:47

    Thanks, @Vishal Soni, @Robbie Duncan, @Kundan Kumar Jha

    for sharing your thoughts! 

     

    I agree that Data 360 is becoming an important skill, especially as Agentforce depends on accurate and trusted data.

    At the same time, I feel Apex, Flow, LWC, and Integration will continue to play an important role in real-time projects.

    Robbie also raised a good point about AI and context engineering. Knowing how to guide and evaluate AI agents will become increasingly valuable. 

     

    My view is that learning one technology is not enough anymore. Understanding how Data 360, Agentforce, and other Salesforce technologies work together will be the real advantage. 

     

    Thanks again for making this a valuable discussion!

Escribir una respuesta...
0/9000
Venkat Yadav (Founder & Lead Trainer en SFDCINDIA) publicó en #Agentforce
16 oct, 07:41

Hi Trailblazers!  

 

If you're planning to learn Salesforce Data 360 (formerly Data Cloud), here is a simple roadmap to follow.

1. Data 360 Basics

  • Introduction, Architecture and Real-Time Use Cases
  • Key Features and Benefits

2. Setup and Data Ingestion

  • Data 360 Setup and Permissions
  • Data Spaces, Data Streams and Connectors
  • Zero Copy Integration

3. Data Modelling

  • Data Lake Objects (DLOs)
  • Data Model Objects (DMOs)
  • Data Mapping and Transformations

4. Identity Resolution

  • Matching and Reconciliation Rules
  • Unified Customer Profiles

5. Insights and Segmentation

  • Calculated Insights and Streaming Insights
  • Segments and Data Graphs

6. Data Activation

  • Activation Targets
  • Data Actions and Flow Integration

7. Data 360 with Agentforce

  • Structured and Unstructured Data
  • Search Indexes and Retrievers
  • Data Libraries and Agentforce Integration

8. Security and Practical Experience

  • Data Security and Governance
  • Monitoring and Troubleshooting
  • End-to-End Real-Time Project

 Useful Learning Resources 

 

🔗 SFDCINDIA – Salesforce Data 360 Blog

https://sfdcindia.com/blog/salesforce-data-360

 

🔗 Salesforce Data 360 Learning Trail

https://trailhead.salesforce.com/content/learn/trails/data-cloud-explore-setup-to-activation

 

🔗 Data 360 Fundamentals

https://trailhead.salesforce.com/content/learn/trails/unlock-your-data-with-data-cloud

 

🔗 Salesforce Official Documentation

https://help.salesforce.com/s/articleView?id=data.c360_a_data_ingestion.htm&type=5

 

🔗 Data 360 Consultant Certification

https://trailhead.salesforce.com/credentials/data360consultant

 

My Suggestion:

Start with Data Streams, DLOs, DMOs, and Data Mapping before moving to advanced topics.

Focus on hands-on practice and try to build at least one end-to-end project. 

 

 Which Data 360 topic do you find most challenging? 

 

Let's share our experiences and learn together! 

 

#Data Cloud #Data360 #Agentforce #Trailhead Challenges #TrailblazerCommunity

Escribir un comentario...
0/9000
Guilherme Sequine (Marketing Cloud Specialist en Gentrop) preguntó en #Trailhead
15 oct, 18:06
MC Next - SANDBOX Environment

Good afternoon everyone, how are you? 

 

I have a question regarding the following scenario: I have a client who is about to implement MC Next and wants to proceed with development in a sandbox. 

 

In this case, do we need to complete the full MC Next + Data Cloud setup in production first, and then repeat it in the sandbox? Or, once the setup is done in production, will it correctly mirror to the SANDBOX environment? 

 

Because the scenario I encountered was: the client provided the sandbox environment for us to work in, but while setting up MC Next after activating Data Cloud, I ran into some blockers to proceed with the setup. This raised the question of whether it is necessary to do everything in production first before doing it in the sandbox. 

 

Thank you ! 

 

MC Next - SANDBOX Environment

 

 

 

#Trailhead  #Salesforce Developer  #Salesforce Admin  #Salesforce  #TrailblazerCommunity  #Marketing Cloud

3 respuestas
  1. Jonathan Kienzler (Salesforce)
    16 oct, 07:34

    Hi @Guilherme Sequine, here are some of the practices I see most customers adopting: 

    1. SMS: if you have sender codes for Production and Dev use, set up both in Production first, then refresh the sandbox. A code can only be active in one org at a time, so both live in Production but only the real one is active there; in the sandbox, deactivate the real one and activate the test one.
    2. Email: sending domains, From addresses and tracking domains don't copy to sandboxes and can't be deployed between orgs. To send from your own domain, each sandbox needs its own authenticated sending domain; if your sandbox is long lasting and it is relatively easy for you to set a DKIM on your / your customer's domain, a separate subdomain per sandbox keeps it clean. If not, I believe you can activate the "Use a substitute email address for unverified domains" in Setup > Deliverability. It is worth a quick test.
    3. Data 360: provision in Production first, then activate Data 360 in each sandbox separately (if the sandbox exists before Data 360 on Production, activate Data 360 in Production and then refresh the sandbox, or use Match Production Licenses, which can take up to 24h). Connections copy over from Production but come across deactivated, so you need to activate each one. The CRM home connection switches to point at the sandbox org automatically when you activate it.

    There are a lot of helpful videos at this link, including the first one that talks about deployment back to Production: https://help.salesforce.com/s/articleView?id=mktg.mktg_videos.htm&type=5

     

     

    I hope this helps :-)

Escribir una respuesta...
0/9000