Select An Org
Data 360: Person Account Related List Mapping Requirement
Publish Date: Feb 3, 2026
Description
This article is specifically used for identifying issues with no data being returned for when creating Related list on Person Account. You can create related list using Person Account if they are correctly enabled within your org. Person Account related list is either created off of the Contact or Account object via object manager. This article points out why data might not be returning base on the mapping and identity resolution setup that has been established. Below provides the correct mappings/identity resolution setup needed for you to return data within your person account related list.
Resolution
Creating a related list on Contact CRM object when Person Account is enabled will use personContactId from person account to query Data 360 to find engagement data within the engagement DMO. User should have mappings outlined like below:
Creating a related list on Account CRM object when Person Account is enabled will use personAccountId from person account to query Data 360 to find engagement data within the engagement DMO. User should have mappings outlined like below:
Mix-matching these mappings for example (Engagement DMO with AccountId ----> mapped to Individual -----> created unified individual -----> created a related list in contact CRM) ---- This setup would result in no data return since related list off of contact w/ Person Account enabled would mean that the system is using PersonContactId as a PK lookup to look for engagement data in Data 360.
Knowledge Article Number
004269106
Did this article solve your issue?
Let us know so we can improve!
