Skip to main content

Feed

Connect with fellow Trailblazers. Ask and answer questions to build your skills and network.

I’m currently working on the "Add a Flow as an Agent Action" challenge, but I’ve run into a blocker: the required flow (Cancel Contact’s Booking) is not available in my org's Flows.

Here is what I’ve done and checked so far:

  • Prerequisites: All previous units and hands-on challenges were completed successfully and verified.
  • Org Setup: I initially used my assigned Special Developer Edition org, and when that failed, I spun up a brand new Agentforce-enabled Developer org. The flow is still missing in the new org as well.
  • Manual Flow Creation: I attempted to build the flow manually in Flow Builder, but I don't have the required input/output parameter specs (like Booking_ID, Error_Message_Output, and Updated_Booking_Record) to configure it correctly for the agent.

Has anyone else encountered this missing flow asset or figured out a workaround/manual setup for the flow parameters? Any tips or insights would be greatly appreciated 

 

#Trailhead Challenges  #Trailhead

0/9000

Went to do my weekly imports and the import tool could not find the field mappings despite them still being in the Import File mapping fields record. I checked our full Sandbox and the import tool had the same problem, so I can't see this as some sort of human error on our side 

 

#Salesforce Admin  #Trailhead

4 answers
  1. Sep 16, 11:04 PM

    @Deepak Sharma Yes matey, mappings are still associated with the Import Type but they aren't showing where the rubber hits the road. I'm reluctant to rebuild them if I can't be certain they will still be there next week plus there are 40 fields to map twice. **** painful when I only work 3 days a week

0/9000

I’m using Conversation-Level Testing in the new Agentforce Studio Testing Center (Beta) on Summer ’26

I downloaded the CSV template directly from Upload Test Cases → Template, which contains: 

Conversation, Expected Actions, Expected Subagents 

However, after uploading the populated template and running the test, I receive: 

 

Turn-Level Testing works correctly with its corresponding CSV template. 

  

Is there a different column name or CSV format required for Conversation-Level Testing, or is this a known issue with the current Beta Testing Center? 

  

 

#AgentforceTesting  #Agentforce

1 answer
  1. Sep 16, 11:03 PM

    @Bodala Pallavi

     

    What I'd try, quickly - 

    1. Populate the template without opening it in Excel if you can, or re-save explicitly as CSV UTF-8, to eliminate the encoding angle. 

    2. Check the exact header spelling and order against any current Salesforce Help doc for Conversation-Level Testing, in case the tool expects a slightly different header (for example a "Conversation" vs "Conversation Transcript" naming drift between template versions). 

    --> If both check out, treat it as a known Beta issue. Conversation-Level Testing is new in Summer '26 and this is exactly the kind of template-versus-parser mismatch that shows up in Beta.  

     

    Since the template came straight from the tool and Turn-Level works with its template, this points to a Beta bug rather than user error. I'd log it with Salesforce Support, referencing Testing Center Beta, and note that the tool-provided Conversation-Level template is rejected on upload.

0/9000

I have a trailhead module listed under private training as its for Canadian employees only. It's called: Complete Training: Ontario Occupational Health and Safety Awareness. Within the module there is a link to a external website and you have to work through the content and do a test. The webiste keeps crashing and not allowing me to advance for past two weeks, it is not saving my history so I have to keep starting over. I have wasted hours on this. this is the link to the website: https://www.labour.gov.on.ca/english/hs/elearn/worker/foursteps.php

 

 

#Help  #Training

2 answers
0/9000

I just created a new flow that is a after-save record triggered flow. The flow is triggered when a new Opportunity is created. We create Opportunities 3 ways, manually, through our 3rd party donor portal, and through our app. The manually created Opportunities and the Donor Portal created Opportunities are triggering the Flow and it works correctly. But none of the Opportunities created by Zapier have triggered the Flow. Is there something in the way Zapier creates records that would cause the Flow not to recognize a new Opportunity? There is an entry criteria, but several Opportunities met it and did not trigger the flow (from Zapier only).  

 

#Flow

3 answers
  1. Sep 16, 10:39 PM

    Maybe Zapier creates and then updates the Opportunity? It might come in from Zapier at $0, then get immediately updated? Maybe try the following in a sandbox or dev org. Three possible ideas: 

    1. Can you change to update the flow to trigger when a record is created or updated? Or would that not work for your circumstance? 

    2. If you do change it to created or updated, you could select to have it run only when a record is updated to meet the condition requirements, and then make sure the requirements are even more specific. 

    3. OR, instead of doing those two things, try to remove an entry criteria at a time to see if one of the criteria seems to be causing this to happen. 

0/9000

Hello! I recently set it up and configured Agentforce Coworker to work with our Salesforce data, Slack, and our website (via Data 360). After setup and a single day of testing, I found that I used nearly 12,000 Einstein Requests (no other consumption of other credits). My concern is that we'll run out of our 200K allocated Einstein Requests in no time. 

 

Does anyone have advice for keeping credit consumption numbers low? If it makes a difference, we use NPSP and do not have plans to migrate to Agentforce Nonprofit at this time. As a nonprofit organization, I'd love to use this feature, but I'm not sure if I can justify the potential cost. I have a staff of 20 and am trying to determine what a budget might look like. Maybe I need to go a different path with the AI capability available in Salesforce? 

 

I appreciate any and all advice in advance! Thanks!

1 answer
  1. Sep 16, 10:34 PM

    @Matt Devine

     

    Every agent action, grounding retrieval, and reasoning step burns Einstein Requests, and the Data 360 grounding is usually the big driver. When the agent pulls from Salesforce, Slack, and your website on each query, a single user question can fan out into many requests behind the scenes. So the fix is narrowing what the agent reaches for.  

     

    I'd suggest --  

    Start with one scoped use case, measure for a week, and compare that against the lighter Einstein features before committing. That's the only way to get a budget number you can actually defend.

0/9000

Hello! I'm trying to insert the Calendar Link merge field into an MCAE field. When testing the email, I get this error message. I'm not sure what the fix is as I've re-synced the metadata among other things. Has anyone experienced this before or know of a fix? 

 

#Pardot B2b Marketing Automation

1 answer
  1. Sep 16, 10:02 PM

    That does not look like one of the Sender merge fields that you can use. Here is a list of the Sender merge fields: 

    {{Sender.Email}} The sending user’s Email field 

    {{Sender.FirstName}} The sending user’s First Name field 

    {{Sender.LastName}} The sending user’s Last Name field 

    {{Sender.Name}} The sending user’s full name; displayed as: First_Name Last_Name 

    {{Sender.Phone}} The sending user’s phone number 

    {{Sender.Signature}} The sending user’s text signature, available to edit in the user’s profile 

    {{Sender.Title}} The sending user’s job title 

    {{Sender.URL}} Link to your company’s website from assigned user’s URL field 

     

    Found here: 

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

0/9000

Hi People, 

 

I am working on a data cloud implementation. We had a Business unit linked to a Data Space and we deactivated the Business unit. 

 

Now when I try to delete the Data Space, it throws the following error: 

 "Data Space could not be deleted: You can’t delete the

data space 'Canada' because it’s associated with a business unit that has at least 1 CMS workspace

."  

 

Also BU Related Data Kits are deployed. 

 

 

Anybody got any idea on how to fix this? The requirement is to delete the Data Space. 

 

#Data Cloud

1 answer
  1. Sep 16, 9:47 PM

    Hi , 

     

    Deactivating the Business Unit is not sufficient. The Data Space still appears to have a dependency on a Business Unit that contains one or more CMS Workspaces. Check the Marketing Cloud Business Unit for existing CMS Workspaces and remove any remaining Data Space mappings. Also verify whether any deployed Data Kits are still associated with the Data Space before attempting deletion again. 

     

    https://help.salesforce.com/s/articleView?id=004575666&type=1

0/9000
1 answer
  1. Sep 16, 9:36 PM

    You do not need to purchase an add-on license, but you do need a Standard User License and the Customize App perm set.

    If you are using a Trailhead org, it should not be an issue as you usually are given Sys Admin access which gives you access to Schema Builder. Hope this helps.

0/9000

We'd like to turn on the setting to use SLDS 2 for pages that include <apex:slds> when an SLDS 2 theme is active in User Interface in order to take advantage of dark mode and SLDS 2 for our custom Visualforce pages. 

 

However, when we do so, some of our managed package Visualforce pages have significantly degraded appearance. This includes Salesforce's Nonprofit Success Pack Contact Merge page in particular.  

 

Is there a way to enable SLDS 2 on particular Visualforce pages (the ones we have control over) and leave SLDS 1 for the managed package ones that we can't update (and may not be able to get Salesforce to update)? It looks like there is a way to force <apex:slds> to use SLDS 1, but that doesn't really help us as we can't edit the managed packaged pages where that would be necessary. 

 

I can try opening a Salesforce support case, but since they started replacing everything with AI, it's been much more difficult to get a decent response. I suspect the answer will be to create an Idea, which will then languish for years or just be closed (which doesn't really help solve our problem).  

 

@Nonprofit Success Pack @Design Trailblazers

1 answer
  1. Sep 16, 9:21 PM

    Hi , 

     

     

    Unfortunately, I don't believe Salesforce currently provides a way to selectively enable SLDS 2 for some Visualforce pages while forcing managed-package Visualforce pages to remain on SLDS 1. If a managed package page such as NPSP Contact Merge is broken by SLDS 2, this is likely an issue that must be addressed by the package provider or Salesforce itself.

0/9000