Expand my Community achievements bar.

SOLVED

New Field Group Not Appearing in Dataset After Data Ingestion

Avatar

Level 1

We have added a new field, des_exclusion, to our Individual Profile - AJO Jump Schema, along with a new Field Group: Exclusion Flow, which contains this field.

After ingesting data that includes values for des_exclusion, we noticed that when querying the dataset associated with the schema, the new Field Group and the field do not appear in the records, even though the ingestion was completed successfully.

We have verified that:

The schema structure has been correctly updated with the new Field Group.
The dataset is still linked to the correct schema.
The data ingestion process was completed without errors.
Are there any additional steps we need to take to ensure the dataset reflects the new field and Field Group? Could this be related to the profile enablement process in Adobe Experience Platform?

Any guidance on this issue would be greatly appreciated.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @Franklin_AaronCu  - Please check the mapping once if it has been mapped with right path and ingested the data. Some cases we may use the old or wrong path to ingest the data. I would request you to use a retrieve mapping API to check the mapping path. Also, not sure if you are intended to enable the profile for ingestion. if you are fine, then create an audience by utilizing the field that has been just ingested with new data.
 
Thank you,
Jayakrishnaa P.

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Hi @Franklin_AaronCu  - Please check the mapping once if it has been mapped with right path and ingested the data. Some cases we may use the old or wrong path to ingest the data. I would request you to use a retrieve mapping API to check the mapping path. Also, not sure if you are intended to enable the profile for ingestion. if you are fine, then create an audience by utilizing the field that has been just ingested with new data.
 
Thank you,
Jayakrishnaa P.