Skip to main content

#Agentforce322 personnes en discutent

Agentforce is an umbrella term of the set of tools to create and customize agents as well as the collection of agents Salesforce provides across the Customer 360. Agents can either be autonomous or assistive.

Hi Trailblazers,

I missed  the event code of today’s AI Force workshop. My org has since closed, and to reopen it and try the hands-on exercises, I need that code.

If you attended the event today, could you please share the event code with me?

Thanks in advance for your help! 

 

#Salesforce Developer  #Agentforce  #Trailhead  #AI  #Hands On Workshop

0/9000

Hello,  

 

I have hit a wall when it comes to deploying my agent as part of the Headless Use Case Trail. I keep getting the attached error message, can anyone advise?  

 

Thanks in advance  

Error Message - Headless Use Case: Use a Conversation to Build an Agent

 

 

 

#Help  #Trailhead Challenges  #Agentforce

6 réponses
  1. Hier, à 14:30

    Support were able to find a solution. I was advised to enable the Einstein Bot and relaunch my playground, worked perfectly and I was able to complete my AgentBlazer Innovator badge! 

0/9000

Agentforce Builder fails right after naming the agent? Check your sandbox File Storage

 

The symptom

In a Developer sandbox, nobody could create a new agent in Agentforce Builder, admins included. You type the agent name, click next, and a red banner says the agent couldn't be created and to contact your Salesforce administrator. Nothing else: no error code, no detail.

We lost a few days to it, so here is what we found.

What we ruled out first

  • Permissions and licenses. It failed for every user, including System Administrators with the Agent Platform Builder permission set and license.
  • Org settings. Agent Platform and Einstein generative AI were both enabled.
  • Validation rules and triggers on User. None applied.
  • A CLI clue that pointed the wrong way. We reproduced the failure with sf agent publish authoring-bundle. The debug log showed a 404 from the agent authoring API, followed by a timeout on a sandbox fallback host. It matches an open CLI issue (forcedotcom/cli #3634), and we almost opened a support case over it. In our case it was not the cause.

The clue that mattered

Each failed attempt still created the agent's run-as user ("EinsteinServiceAgent User") and assigned its licenses and permission sets. Setup Audit Trail showed every step succeeding. So the failure happened later, when the agent itself was saved.

Then we checked the org limits:

 

 

sf limits api display -o <sandbox> | grep -i storage

File Storage: 248 MB used of 200 MB (124%).

One presentation file, a little over 240 MB, had been uploaded to the sandbox weeks earlier. Developer sandboxes allow only 200 MB of file storage. Once you're over the limit, the org refuses new files. We confirmed it by inserting a 1 KB ContentVersion, which failed with STORAGE_LIMIT_EXCEEDED. According to Salesforce Help, when data or file storage is over 100% in a sandbox, record creation can fail too, not just file uploads.

The timeline matched: the last successful agent save was before that upload, and every failure came after it.

The fix

  1. Find the largest files: 

     

     

SELECT Title, FileExtension, ContentSize, CreatedDate

FROM ContentVersion WHERE IsLatest = true

ORDER BY ContentSize DESC LIMIT 10

Download what you need to keep, then delete it from the org.

  1. Empty the Org Recycle Bin. Deleted files still count toward storage until the bin is emptied.
  2. Try again. With storage back under the limit, agent creation went through.

Clean up afterwards

Every failed attempt leaves an orphaned, active agent user, plus its permission set and license assignments. We had 12. Find them with:

 

 

SELECT Username, CreatedDate, CreatedBy.Name

FROM User

WHERE Profile.Name = 'Einstein Agent User'

ORDER BY CreatedDate DESC

Make sure no agent references them, then deactivate them.

Takeaways

  • In Agentforce Builder, a generic "couldn't create the agent" banner can hide a storage problem, not just permissions.
  • Developer sandboxes have small storage limits (200 MB data and 200 MB file storage). One large deck or recording is enough to hit the file limit.
  • Check sf limits api display early. It takes seconds and would have saved us days.

A note on certainty: we confirmed the root cause by removing it, since agent creation worked again right after the cleanup. We haven't seen it documented by Salesforce. If you've seen the same thing, please add it below.

 

 

 

#Agentforce  #Sandbox  #Salesforce CLI  #Storage Limit

0/9000

Cue the confetti, Trailblazers! Together, you’ve officially earned 1.

 

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

0/9000

Hi! I'm struggling with object handling in Agent Script. Is it possible at all? i've tried using dot notation and bracket notation to populate a key, but to no avail. Can someone offer info or documentation regarding this? Thanks in advance 

 

#Agentforce

2 réponses
  1. 20 oct., 17:09

     Agent Script does NOT support direct dot/bracket notation to write into object variable properties. This is a known limitation.

    Here's what the official docs actually say about 

    object

     type variables:

    What IS supported:

    Agent Script supports these variable types: 

    string

    , 

    boolean

    , 

    number

    , 

    object

    , and 

    list[type]

    . You can declare an 

    object

     variable like this:

    variables:

    CandidateList: mutable list[object] = []

    description: "List of contacts returned from an action"

     

    How objects actually get populated — only via action outputs:

    The only supported way to populate an 

    object

     or 

    list[object]

     variable is by capturing it from an action's output using 

    set

    :

    reasoning:

    instructions: ->

    run @actions.Get_Questions

    with JobScreeningRecordId=@variables.JobRecordID

    set @variables.questions = @outputs.AllScreeningQuestions

     

    You cannot do 

    @variables.myObj.someKey = "value"

     or 

    @variables.myObj["someKey"] = "value"

     — the language has no write syntax for individual object properties.

    What you CAN do with objects after storing them:

    • Read them in LLM prompts: 
    {!@variables.questions[@variables.current_question]}

    Pass the whole object as an action input

    • Use 
    len(@variables.myList)

     on a list of objects

    The workaround:

    If you need to build up a structured object with specific keys, the correct pattern is to:

    1. Use separate primitive variables ( 
    string

    , 

    boolean

    , 

    number

    ) for each field you need to track

    1. Pass those individual variables as inputs to an action that assembles the object server-side (Apex/Flow)
    2. Store the assembled result back via 
    set @variables.result = @outputs.assembledObject

    Docs references:

0/9000

Good morning, 

 

In my organization, one user is unable to see shared dashboards on their home page (they can only see them in the Dashboards menu). 

 

Could you provide some suggestions for resolving this issue? Thank you. 

 

#Trailhead  #Salesforce Developer  #Salesforce Admin  #Agentforce

4 réponses
  1. 20 oct., 10:01

    Hello, 

     

    I tried and verified all the suggested solutions, but none of them worked. 

     

    I resolved the issue immediately by deactivating the affected user and creating a new user with the same name. 

     

    It worked. 

     

    Best regards

0/9000
7 commentaires
0/9000
3 réponses
0/9000

Hi Team, 

 

Q1: I am getting below error while checking challenge for Build an AI-Generated Summary of Related Records superbadge: 

Error: We can't find the Interest Summary field enabled for use with Einstein Generative AI. 

Where can I find the option to enable generative AI for the custom field Interest Summary. 

Q2: For Create a Prompt Template for an Engagement Email which template type I need to choose and what would be the placeholder text? 

 

Thanks, 

Indira Mathur 

 

#Agentforce

2 réponses
  1. Hier, à 16:58

    Hi @Indira Mathur, 

    Please follow below steps to solve this:

    1. Upgrade the Record Detail page to Dynamic Forms
    2. Select the Interest_Summary__c field and choose the newly created Prompt Builder
    3. Save the changes and see the GenAI in action on the said field.
0/9000

Hi Trailblazers, 

 

I recently started exploring Agentforce through Trailhead and found it very interesting.

I have basic knowledge of Salesforce objects, relationships, Flow Builder, and Permission Sets.

But when I started exploring Agentforce, I came across topics like Agent Actions, Subagents, Prompt Templates, and integrations.

Do I need Apex and integration knowledge before learning Agentforce, or can I start with my current Admin skills?

What would be a good learning path for beginners? 

 

Thanks in advance! 

 

#Agentforce

1 réponse
  1. Hier, à 10:42

    Hi @Chaitanya d

    Yes, you can start learning Agentforce with basic Salesforce Admin knowledge. Apex and Integration skills are not mandatory for beginners. 

     

    1. Recommended Learning Path:

    • Salesforce Admin: Objects, Relationships, Security, and Flows.
    • Agentforce Basics: Agents, Subagents, and Actions.
    • Prompt Builder: Prompt Templates and Grounding.
    • Agent Actions: Start with Flow-based actions.
    • Advanced Topics: Apex, APIs, Integration, and Data 360.

    2. Start with Small Projects:

    • Build an Employee Agent to summarize Account records.
    • Create a Flow-based action to retrieve Contact details.
    • Build an agent that creates a Case using Flow.

    Start with Admin + Flow + Agentforce. Once you're comfortable building and testing agents, gradually learn Apex and Integration for advanced requirements. 

     

    Salesforce Documentation:

    Related Trailblazer Discussion:

    Don't wait until you learn everything. Start building small agents and improve your skills through practice.

    All the best!

0/9000