Skip to main content

Title:

Data 360 Trailhead Issue: Contact_Home Mapping Warning 

Identity Resolution is

Published and Succeeded, but I still have a Contact_Home data mapping warning. When attempting to change the mapping from Contact ID → Individual Id to Individual ID → Individual Id, I get:

Because of this, the flow debug fails with:

Has anyone successfully completed this project and found a workaround for this issue without recreating the playground? 

Stuck on Trailhead project

 

 

Screenshot 2026-10-06 144446.png

 

 

 

#Trailhead Challenges  #Data Cloud  #Agentforce  #Data360

1 respuesta
  1. 6 oct, 09:59

    Hi Aniket, 

     

    Worth reconsidering the fix itself before fighting the DeveloperEdition restriction: per Salesforce's own official Contact DLO-to-DMO mapping reference,

    Contact.Id mapping to Individual.Id

    is the standard, correct mapping — that's exactly what you already have. Switching it to "Individual ID → Individual Id" isn't the documented fix; you may be chasing the wrong field. 

     

    The warning text itself is the clue: "Map all required fields to create your unified profiles" — that's a field-completeness warning, not necessarily a primary-key mismatch. Go into the Contact_Home mapping (Data Model → Individual DMO → Manage/Edit mapping for Contact_Home) and check whether other required fields besides the ID (typically First Name, Last Name) are actually mapped, not just the primary key. That's the far more common cause of this exact warning — an incomplete field mapping, not a wrong ID field. 

     

    On the "Switch Mapping is not supported on DeveloperEdition" error: that's a real, known platform restriction — changing which field/DMO a DLO is mapped to after initial mapping is a reconfiguration action that Data Cloud restricts on free Developer Edition trial orgs. Since that path is blocked by design, not by something you're doing wrong, it's not something to work around — it's confirmation you were on the wrong track trying to switch it in the first place. 

     

    So: leave Contact ID → Individual ID as is (it's correct), and instead fill in whatever other required fields are unmapped on that same Contact_Home → Individual mapping. Re-run the Identity Resolution ruleset after that, and the warning should clear without needing the switch at all.

0/9000