#Trailhead Challenges토론 중인 항목 1,426개

Hi Tierra, 

Per the official Salesforce documentation: "When prospective customers fill out a form on your LinkedIn ad, we convert the data directly to new leads in Salesforce." So the native LinkedIn Lead Gen Forms integration always creates a new Lead record, it doesn't check against existing Contacts first, which lines up with what Aman mentioned. 

Reference:

To document a form fill on an existing Contact's record instead, here are your options, in order of effort: 

1. Manual match-and-convert (lowest effort, no extra tools): 

   Set up a report or list view filtered on Lead Source = LinkedIn, reviewed periodically. When a new LinkedIn Lead matches an existing Contact by email, use standard Lead Conversion and choose "Attach to existing Contact" instead of creating a new one. Not real-time, but zero extra build. 

2. Automated matching via Flow (moderate effort, native only): 

   Build a Record-Triggered Flow on Lead (After Save) that searches Contact by Email. If a match is found, auto-run Lead Convert pointed at that existing Contact, and log an Activity/Task on the Contact noting the LinkedIn form submission details. This gets you close to real-time without a third-party tool. 

3. Third-party connector (what Aman flagged): 

   Tools like LeadsBridge offer built-in "search Contact first, only create Lead if no match" branching out of the box, but bringing in a whole platform just for this one gap is real overhead if it's your only need. 

Given you're already this deep into setup, option 2 (Flow-based auto-match-and-convert) is the best native middle ground, no new licenses, and it directly solves documenting the form fill on the existing record without manual review.

Hey Michelle, 

Superbadge units are structured as: read the scenario/requirements first, THEN there's a hands-on challenge. What you're describing (a "500 points, Assessment Complete" screen appearing before you did any actual configuration) suggests this first unit is a knowledge-check/read-through type assessment rather than a hands-on build challenge, some Superbadge units are just verifying you reviewed the scenario, not that you built something yet, the real hands-on work starts in later units like "Translate Text with a Prompt Template and Record-Triggered Flow." 

If that's the case here, nothing actually went wrong, you're not missing work, this unit's "challenge" may have simply been confirming setup/connection to your Dev org, and the real building starts next. 

To confirm: click into "Retake this Challenge" and read exactly what it's asking you to do, if it only asks you to review requirements or confirm org connection (not build something), then the 500 points are legitimate and you should proceed straight to the next unit. 

If you genuinely believe this unit requires hands-on work you skipped, compare the unit's written instructions against what's actually in your org (any Prompt Templates, Flows, etc. expected). If nothing was supposed to be built yet, proceed forward, the units in this Superbadge build progressively, so nothing later should be blocked by this one being "too easy." 

Reference:

For the OwnerId variable, selecting $Record and then the variable named "Owner" with the subtitle "Owner Id" causes the error discussed, likewise with the WhatId variable.

To resolve the error, after selecting the variable named "Owner", I also selected the variable named "Id", likewise for the "Account" variable.

The instructions in the unit Build a Record-Triggered Flow, 

• OwnerId = $Record > OwnerId
• WhatId = $Record > AccountId

did not explain the steps I used that resolved the errors.