Identity namespace should be same for the identities?

[ADLSSt200]

Hi, I am creating two schemas individual profile and experience event schema and using loyalty_Id as identity in the both schema. Whether should I create single namespace for both the Ids or create two namespace to assign them separately?

[Tof_Jossic]

@ADLSSt200 the same namespace should be available to use in both Profile and Event schemas

[ADLSSt200]

Thank you! I did the same and when I ingested data and validated it in profile by searching an identity and its namespace ... it's showing attributes only not the event for the event schema 

And in identity graph only one dataset is showing there why other one dataset is not there and I think identities aren't getting stitched. How to solve this problem?

[Tof_Jossic]

@ADLSSt200 might be tricky to fully troubleshoot here but I'm trying to trace your data off of those screenshots. As far as I can tell, the Identity Graph contains 2 identities stitched together which I believe are 'loyaltyid' and 'crmid'.

In terms of the events, it looks like you are uploading via file upload into dataset 'Luma Offline Purchase Events Dataset - Vishal'. As far as I can see the data lands into the Data Lake but is not being promoted to UPS.

It looks like the dataset was enabled for Profile after the data started ingesting, that would be the issue.

[ADLSSt200]

I have tried enabling the dataset before ingestion but still same issue. But when I created merge policy there was an error "The merge policy is being used doesn't support lookup data." when I checked an event of an identity(the previous error in image shared. And when I search event schema identity in graph viewer it shows nothing. Can you please help me how to resolve this issue due to this I am not able to create audience too.

Here is what I have done-

• I created schemas "Luma Loyalty", "Luma CRM" and "Luma Offline Purchases", assign the identities and same namespace across schemas for the corresponding ids.
• "Luma Loyalty" has Loyalty Id and CRM Id, "Luma CRM" has CRM Id, and "Luma Offline Purchases" has Loyalty Id as their Identities.
• Even the identity attribute names were same in different schemas and enabled them for profile.
• Created datasets, enabled them and ingested the data successfully.
• Created a default merge policy for dataset precedence.
• When I search any identity in the browse tab it shows only the attribute data for "Luma Loyalty" Dataset.
• In the graph viewer it's showing the identity from "Luma loyalty" dataset 

[Tof_Jossic]

@ADLSSt200 I believe the event ingestion fails to promote the data to Profile with the following

"code": "UPINGT-007003-400"

"message": "RelatedEntityIdentityField: List(identityMap) is/are not present in the schema."

At this point, I'd ask you to raise a Support ticket so the team can take a closer look at this at all the elements.

[ADLSSt200]

Okay thank you so much for the resolution, may I know why event ingestion fails to promote the data to profile? Is it kind of a system issue/background issue?

[Tof_Jossic · Accepted solution]

@ADLSSt200 I suspect you have something in your payload that is not in the schema but as I said a Support ticket will allow for a deeper dive at this stage.

[ADLSSt200]

Okay thank you! will check that