Profiles keep getting disabled and not visible in Profile section after ingestion

[Aditi_Londhe]

I am facing an issue in AJO where, after creating a dataset and enabling it for Profile, the Profile option gets disabled again whenever I refresh or reopen the page.

Additionally, when I ingest profiles into the dataset (via Postman), the data appears successfully under the dataset. However, when I try to search for the profiles in the Profile section (using the email address), I am unable to see them.

Could someone help me understand why:
1. The Profile setting is not staying enabled after refreshing?
2. The ingested profiles are not visible under the Profile section even though the data is showing in the dataset?

The same happened with Journey created using event, the profiles entered the journey and also seen under dataset, but the event name is not visible under the profiles I ingested from postman.
Any guidance would be greatly appreciated.

[DavidKangni]

@Aditi_Londhe 

Can you check if the schema is profile enabled?

AEP/AJO has the datalake and UPS. All data ingested are in the datalake but not a Profile level (UPS) if the schema and dataset are not enabled.

Thanks,

David

[Aditi_Londhe]

Hello,

Yes, schema is enabled for profiles.

The problem occurs for dataset; the dataset again and again gets disabled for profile.

[Anuhya-Y]

@Aditi_Londhe May I know the schema type? is it an event type? make sure _id is unique in the event payload. If it is not unique,  data is visible in dataset, but not reflected in profile.

https://experienceleague.adobe.com/en/docs/experience-platform/xdm/classes/experienceevent 

[Mayank_Gandhi · Accepted solution]

@Aditi_Londhe  you can check a similar thread here https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-26352

Many event-based datasets are not enabled for Profile by design, so their data appears in the dataset but not as profile attributes.