#Trailhead Challenges2,023 discussing

Hi @shiva shankar

The error "no results found for email object in Salesforce" when previewing your Conga email template typically happens when the template can't find the required data in Salesforce. This could be due to issues with data sources, object references, or missing records. Please verify the following:

1. Missing Data: The email template may be linked to an object (e.g., Lead, Contact, Account), but no data is available in Salesforce for the preview. Ensure the object has at least one record with populated data, and that any merge fields you use are correctly populated in the relevant record.
2. Incorrect Merge Fields: If the merge fields reference non-existent or incorrect fields, the data won’t be pulled. Double-check that the merge fields are mapped to valid fields in the correct object.
3. Selecting a Record for Preview: When previewing, ensure you select an existing record with data that matches the criteria for the email template. You might also need to specify a record ID for the preview to display data.
4. Permissions: Ensure you have the necessary permissions to view the records and data in the relevant Salesforce object. If permissions are restrictive, the email template may not be able to find or display the data.
5. Conga Configuration: Review your Conga configuration settings to ensure Conga Composer is correctly set up to pull data from the correct Salesforce data source. You may need to verify the configuration for the data sources and data model.

Refer to the following documentation for more details: 

Hope this helps. Thanks!

Hi, 

First, the fact that you're learning daily and participating in the 100 Days challenge already puts you ahead of most people starting out. Now let's figure out the right direction. 

The three main Salesforce career tracks 

Admin track — configuration, automation (Flow), reports, dashboards, user management. No coding required. Best for people who enjoy solving business problems through point-and-click tools and understand how businesses work. Entry cert: Salesforce Administrator.

Developer track — Apex (Java-like language), Lightning Web Components (JavaScript-based), APIs, integrations. Best for people who enjoy coding or come from a programming background. Your profile mentions Full-Stack Dev, which means this track would feel natural to you. Entry cert: Platform Developer I.

Consultant track

— implementation, requirements gathering, solution design. Best for people who enjoy client-facing work and strategic thinking. Usually requires Admin + domain knowledge first. 

Recommendation for you 

Since you have a Full-Stack development background, the Developer track is your strongest starting point. Your existing JavaScript knowledge maps directly to LWC, and learning Apex is straightforward if you know any object-oriented language. Developers consistently command higher salaries than admins in most markets, and the combination of Admin fundamentals + Developer skills makes you extremely versatile on project teams.

Start with Admin fundamentals on Trailhead (you need this foundation regardless of track), then move into the Apex and LWC modules. Aim for Platform Developer I as your first certification after Admin. Build 2-3 portfolio projects in a free Developer Edition org — even simple ones like a custom app with Apex triggers and LWC components.

Keep going with the 100 Days challenge — consistency is what separates people who break into Salesforce from those who don't. You're on the right track.

This is a common issue with the Advanced Flow for Agentforce Superbadge Challenge 2. The 'Last Customer Verification' field may not appear due to a field mapping issue in the Update Record element. Here's how to fix it:

Steps to resolve:

1. In the Flow, open the Update Contact's Last Customer Verification Update Records element.

2. Click Add Field and manually search for "Last_Customer_Verification__c" using the field search box - it may not auto-populate in the dropdown.

3. Verify the Contact object is selected correctly as the record to update (it should filter by the Contact ID from the preceding Get Records element).

4. If the field still doesn't appear, check that the Last Customer Verification custom field exists on the Contact object in Setup. Go to Object Manager > Contact > Fields and Relationships and confirm it's present.

5. Save and re-open the flow - sometimes the field picker refreshes after a save.

If the issue persists after 48 hours, open a Trailhead Help case at https://help.salesforce.com/s/support.

@Tanushree Debnath this is a Lead Conversion field mapping issue.

The error is specifically saying that Salesforce needs a value for this Account field during conversion: Account.Support_Plan_Expiration_Date__c

To fix it, create a matching custom field on Lead, then map it to the Account field.

Go to: Setup -> Object Manager -> Lead -> Fields & Relationships -> Map Lead Fields

Then map the Lead field to: Account.Support_Plan_Expiration_Date__c

Salesforce’s lead field mapping help explains this process here: (Salesforce)

Also check whether Support_Plan_Expiration_Date__c is marked as required on Account, or required by a validation rule. If it is required, the Lead must have a valid value before conversion, otherwise the Account cannot be created.

There are similar community posts for this same lead conversion mapping error here: (trailhead.salesforce.com)

After mapping the field, update the Lead with the support plan expiration date and try converting again.

The "We can't find an element called Create Refund Request, or it's not built according to the specified configuration" error in Superbadge Challenge 3 is typically caused by one of these issues:

1. Element Label vs. API Name mismatch: The challenge validation checks the element's Label exactly. Verify that the Create Record element is labeled exactly "Create Refund Request" (check for extra spaces, different capitalization, or a typo like "Refund Requests" vs "Refund Request").
2. Object Type mismatch: Confirm the Create Record element is creating a record of the correct object type specified in the challenge requirements (e.g., ensure it's creating a "Refund Request" custom object, not a related object).
3. Field mapping configuration: The validation error "not built according to the specified configuration" often means a required field mapping is missing or incorrect. Double-check each field in the element — the Field and Value mappings must match what the challenge requires exactly.
4. Flow version issue: Even though your flow is activated, ensure you're viewing the latest activated version. If you made changes after activating, the active version may not have your latest edits. Deactivate, make changes, then Save & Activate again.
5. Re-challenge after waiting: Sometimes the Trailhead challenge validator needs a moment after activation. Try clicking "Check Challenge" again after confirming the flow is activated and the element setup is correct.

The most common fix is a label mismatch — copy the exact label text from the challenge requirements and paste it into the element's Label field in Flow Builder.