Feed

Hello @Diana Georgieva

To report on opportunities not created at Lead conversion using the "Created by Lead" checkbox- 

1. Custom Report type- 

Create a report with Lead as the primary object linking Accounts and Opportunities via "Converted Account" and Converted Opportunity". 

Include fields: Lead   ID , Converted Date, Account ID,  Opportunity   I, "Created by Lead" checkbox, and Amount Stage. 

Use "with or without " related records. 

2. Joined Report: 

Use the custom report type with two blocks: Leads(Converted=True) and Opportunities 

(Created by Lead=False for direct creations). 

Correlate manually using Account ID/Opportunity ID. 

3. Filters: 

Add date filters(e.g., Converted Data, Created Date) and "Created by Lead" to track origins. 

4. Export to Excel for manual correlation or use a formula field. 

5. Group by "Created by Lead" and Stage. Use a summary formula(Closed Won COUNT/total COUNT) for win rate. 

Add to a dashboard for visualization. 

Hi @Ankit Lohia

This usually happens when the org is still being set up on Trailhead’s backend. Try:

1. Waiting 5–10 minutes and then refreshing.
2. Trying a different browser/incognito mode.
3. If it still doesn’t load, raise a case via the Trailhead Help page.

Hope this helps!

Hi @Mukund Rathi

Please check with these solutions here -

Thanks!

I have the same problem with the partner GTM resouces, did you get this fixed?

Hi @Sabarish R

Thanks for your message!

To access and modify the Route List Template, you’ll need to have Salesforce Maps installed in your org. If you’re not seeing “Salesforce Maps” in Setup, it likely means the Maps package isn’t installed or your profile doesn’t have access.

Here’s what you can do:

1. Confirm with your Salesforce Admin if Salesforce Maps is installed and licensed in your org.
2. Once confirmed, go to:
   • Setup → Search for Salesforce Maps → Open Route Settings or Templates.
3. Make sure the Address Field is included in your Route List template so it shows in routes.

Let me know once Maps access is confirmed — I’ll help you with the exact steps after that!

I’ve run into similar issues. A few things for you to double-check: 

Make sure the form’s fields exactly match the data extension’s field names and data types, any mismatch can block data flow. Also, verify that the data extension is sendable and linked to a subscriber key or contact key. 

If you’re using an Interactive Email Page, confirm the form’s Submit action is properly configured to update the correct data extension. Sometimes the form defaults to a different DE or none at all. 

Another common snag is permissions, check that your user has write access to the data extension and that the data extension is in the correct folder accessible by the form. 

If all looks good, test with different subscriber keys or contacts to see if the issue is related to key mismatches or duplicates. In my experience, it’s often a small mapping or configuration detail causing the block.

Hello all, 

Thank you for your feedback. 

 I've resolved the issue, and here’s a quick summary of the root causes and fixes:

🔹 Cause 1:

I initially cloned my flow from a standard flow that was configured to use the

action. 

In the flow settings, I deleted the pre-filled values in the original flow field. This allowed me to create new variables and correctly mark them as

🔹 Cause 2:

I replaced the

--> Additional tip:

To avoid flow execution issues, make sure your

. 

Steps:

1. Go to Setup → Process Automation Settings
2. Enable the checkbox: "Let admins debug flows as other users"
3. Then, when debugging the flow, choose the option "Run flow as another user" and select your Agent user.

Hi, 

Merging developer orgs isn’t really something Salesforce supports directly. Each dev org is separate, so you can’t literally merge accounts or data between them. What you usually do is pick one org as your main workspace and manually move or rebuild your work there. 

For your superbadge challenges, the best way is to pick one developer org and use it exclusively for the whole badge. If you have components or data spread across orgs, you’ll need to recreate or deploy them into the single org you’ll submit from.

Hello, 

I've updated my post.