Feed

This is the error i get, in spite of following everything correctly 

Step not yet complete in Agentforce

In the route work component named Route to ESA, we can't find the Agentforce Service Agent set to CC Service Agent. 

I have quite a few DLRS's set to run in "Watch and Process" (Scheduled) mode with a cron that runs hourly during the work day. I often see 1 batch fail due to "First error: dlrs:Too many query rows: 50001". Recently I have seen several batches failing each hour. Previously my Scheduled Job Scope Size was 16 and have reduced it to 8, but the number of batches for the hourly job have not doubled (which I would think it would, with cutting the batch size in half), nor have the failed batch number been reduced. Typically, there are between 60-100 Total Batches, but can go as high as 500 if a lot of activity. Do I have to reschedule the cron for the new job scope size to take effect? Or any other reason why a change in the Scheduled Job Scope Size is not having an impact?  

Also, when there is a failed batch, does it get re-tried the next time the cron runs?

Preciso de ajuda.  

já tentei fazer conexões via sandbox, production, custom e project default, porém sempre me retorna algum erro do tipo. Não consigo continuar minhas trilhas de desenvolvedor 

We want to use Salesforce to capture visits to our tradeshow booths from both existing and new customers and directly log in potential opportunities. Our contract developer isn't sure how best to build this using just Salesforce. I was wondering if it's a junction object to connect different campaigns to different trade show activities. Or I feel like we could use Pardot form in Kiosk mode but if they are already existing customers we will asking them for data we technically already should have. Anyone have a great system they want to share and how did you build it?

I have tried in a new playground as well but I continue to get this error when trying to complete my "Ehnance Agentforce to Act on Data with Conversational langugage" course. 

• Because the sObjectOutputReference field is set, you also need to set the following fields: object.

#Trailhead Challenges

We have a Wealth Group in our bank that manages about 1300 accounts, and we're transitioning from a legacy system to Salesforce FSC. To capture the notes from the legacy system, they have created .pdf files that we can attach to the Account in SF. However, we need to limit visibility of the file only to the Wealth Group, while keeping visibility of the Account to all users. For example, a customer service rep in a branch should see the Account record, but not the attached file, while a Wealth Group user would see the Account record and the attached file. Is this possible? 

Hi Trailblazers,

I'm facing an issue with OmniStudio Document Generation in a Dev Org (same config as Prod). The document is generating successfully, but it's not getting linked to the Account, and I see this error:

Context:

• The document is generated via OmniScript.
• We are using a Document Generation Action in the OmniScript.
• The Dev Org has the same configurations as Production.
• There's no custom Apex involved.
• We suspect the document is not being linked to the Account properly, possibly due to a failure in DataRaptor or Integration Procedure.
• The user has full access to all related objects like ContentDocumentLink, Account, etc.

🧩 What I’ve Checked:

• Permissions to related objects (Account, ContentDocumentLink, ContentVersion)
• Verified the OmniScript and Document Action setup
• No errors in template generation itself — only during record creation

 Question:

• Where exactly can I find or debug the DataRaptor or Integration Procedure that links the document to the Account?
• What fields must be set (e.g., LinkedEntityId) to ensure linking works?
• Is there a common config or mistake that might cause this error in OmniStudio setups?

Any guidance or checklist to trace this would be super helpful.

Thanks in advance! 🙏 

We transact the majority of our business through channel partners. For a few reasons, we have crafted unique product codes for each our of core products, for example   

• Core product:  NSC-product-info
• Partner A Product:   NSC-PTRA-Product-info
• Partner B Product:   NSC-PTRB-Product-info

In this configuration we are "fulfilling" order with 3 dfferent product even if they are all the same behind the scenes. Analytically this is challenging because I get metrics related to 3 different product when I really want o view them as a single thing    I am considering making the partner products BUNDLES that include just the core product, so that when it is "fulfilled" it would use the core product and my analytic would be easier?    Is this a desirable approach? Will it work? I am open to other ideas as well. Thanks.     

We can’t find the benefit 30-Day Extended Return Period on All Orders associated with the Silver tier and Gold tier. Make sure the priority is selected as 1.

#Trailhead Challenges