#Agentforce307 人正在讨论

Hi @Mohit Kumar Garg

Enabling Einstein for Sales

alone may not be enough for the option to appear in Prompt Builder. 

A few things you can check:

1. In Setup → Einstein for Sales, make sure the Sales Emails feature is enabled.
2. Assign the Prompt Template Manager permission set to the user who is creating the prompt template.
3. For users generating the emails, check whether Prompt Template User and the required Einstein Sales Emails permissions are assigned.
4. Also verify that your org has the required Salesforce license/entitlement for Sales Email functionality.

One more thing — in Prompt Builder, the option is usually shown as Sales Email, not “Email Sales.”

After checking the above, refresh the org or log in again and go to: Prompt Builder → New Prompt Template → Template Type → Sales Email 

If it is still not showing, I would mainly check the org license and permission-set license assignments, as this is often related to feature entitlement. 

Thank you, 

Venkat Yadav.

Sometimes these errors happen randomly.   

If you have entered everything correctly and all the api names are

exactly as they should be from the module instructions, I have found that it can sometimes be resolved by:

1. opening an incognito chrome browser
2. logging into Trailhead
3. re-launching the playground
4. re-verifying the challenge in the incognito browser

Hi @Iris Matthey-Jaquet

Yes, you can use Orders or Closed Won Opportunities as the purchase source. However, an unconverted Lead has no standard relationship to an Account, so a standard report/cross-filter cannot reliably check the Account’s purchase history.

If unconverted Leads must be included, you’ll need a reliable Lead → Account relationship (for example, populated via Flow), and then a Custom Report Type can be used to report on the related purchase data.

So, without creating a relationship/field, the complete requirement cannot be reliably achieved.  

 If this helps resolve your issue, please consider marking it as the Accepted Answer so it can help other Trailblazers as well. Thanks! 

Hi @Prasanna lakshmi Gadela

If you are a beginner in Apex, start with small real-time requirements before moving to advanced topics. 

Some good practice scenarios are:

1. Update one field based on another field.
2. Prevent duplicate records using Apex.
3. Create a related record automatically.
4. Update parent records when child records change.
5. Write a trigger for before insert and before update.
6. Send an email based on a business condition.
7. Write a simple SOQL query with filters.
8. Practice bulk processing using Lists, Sets, and Maps.
9. Create a simple Apex class and call it from Flow.
10. Write test classes and understand code coverage.

Also practice proper bulkification, governor limits, exception handling, and trigger best practices

from the beginning. 

Once you are comfortable with these, you can move to integrations, asynchronous Apex, batch Apex, queueable Apex, and advanced design patterns. 

Here are 2 simple beginner Apex mini-project requirements: 

1. Student Registration Management
   • Create a Student__c record using Apex.
   • Prevent duplicate students based on Email.
   • Automatically set Status = Active when a student is created.
   • Write a test class for the logic.
2. Account Contact Automation
   • When a new Contact is created, check whether the related Account has a phone number.
   • If the Contact phone is blank, copy the Account phone to the Contact.
   • Make the code bulk-safe.
   • Write a test class covering single and multiple Contact records.

Thank you, 

Venkat Yadav.