Skip to main content
S
SantoshRa5
Level 3
May 16, 2026
Question

atrribute missing profilesnapshot dataset, exist in XDM union schema

  • May 16, 2026
  • 1 reply
  • 6 views

Hi ​@Community 

I created two fields in a profile-enabled dataset : customer_id (primary string) and customer_number. The dataset is enabled for Profile and upsert. Both attributes are visible in the XDM union schema and in the Profile UI. However, after running the ProfileSnapshot job, the new attribute customer_number does not appear in the ProfileSnapshot dataset and is therefore not available for export. The customer_id (primary attribute) is available in other datasets as well and helps in stitching..

I have verified the dataset and it contains values for customer_number and same is visible in profile UI. Please assist in finding why the profilesnapshot dataset is not getting populated with the new attribute from profile enabled dataset.

1 reply

A
akhil_merupula
Level 3
May 16, 2026

Hi ​@SantoshRa5 ,

 

This is a known behavior in AEP related to how the ProfileSnapshot job populates the export dataset. A few things to check:


1. Schema merge policy and union schema propagation delay
Even though the attribute is visible in the union schema and Profile UI, there can be a delay between when a new field appears in the union schema and when the ProfileSnapshot job includes it in exports. The ProfileSnapshot job runs on a schedule and may not immediately reflect newly added attributes. Check when the field was added vs. when the last ProfileSnapshot job ran if the field was added after the last successful snapshot, trigger a new run and verify the next export.


2. Field-level inclusion in the export dataset schema
The ProfileSnapshot export dataset has its own schema that must include the field. Verify that the export dataset schema explicitly contains customer_number. Navigate to:
Datasets > ProfileSnapshot export dataset > Schema
Confirm customer_number appears there. If the export dataset schema was created before you added customer_number to your profile-enabled dataset, it may not have inherited the new field automatically.


3. Upsert vs. batch ingestion behavior
Since your dataset is upsert-enabled, verify the upsert records containing customer_number were fully processed and merged into the profile store before the snapshot ran. You can check this in Monitoring > Datasets > your dataset to confirm the upsert batches completed successfully with no partial failures.


4. Identity stitching scope
You mentioned customer_id exists in other datasets and helps with stitching. Confirm that the profile records being exported are the same identity-stitched profiles that contain customer_number if stitching is pulling in a different identity fragment that doesn't have customer_number, that field won't appear in the snapshot for those profiles.


Most likely this is either a snapshot timing issue (fix: wait for next run or trigger manually) or an export dataset schema not reflecting the new field (fix: update the export dataset schema to include customer_number).

Terms & ConditionsAccessibility statement

Loading footer...