Add unstructuredContent data type and field groups for Experience Event and Individual Profile - #2253
Merged
kiranmca04 merged 2 commits intoSep 4, 2026
Conversation
…nt and Individual Profile
knarayanan88
force-pushed
the
feature-2252-unstructured-content-fieldgroup
branch
from
September 3, 2026 21:22
7075a6e to
dba3da4
Compare
knarayanan88
marked this pull request as ready for review
September 3, 2026 21:22
kiranmca04
approved these changes
Sep 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #2252
Adds a reusable
unstructuredContentXDM data type carrying a single free-text field (rawText), plus two thin field groups exposing it — one extending Experience Event, one extending Individual Profile. Non-breaking, purely additive.Motivation
Unstructured/semi-structured data ingestion pipelines need a minimal, reusable shape to carry extracted plain text (e.g. a note, review, or message) on either an Experience Event or an Individual Profile record, keyed by an existing identity. Lineage (source dataset, batch id, ingestion timestamp, extraction pipeline version) is intentionally not modeled here — it is already covered by standard Catalog/batch metadata.
Modeling
rawTextas a data type (rather than inlining it into a single field group) lets the identical shape be$ref'd from more than one field group, following the existing pattern wheretool-usageis referenced fromexperienceevent-survey-response-details.Changes
components/datatypes/unstructured-content.schema.json— new data type, single propertyxdm:rawText(string).components/datatypes/unstructured-content.example.1.json— example for the data type.components/fieldgroups/experience-event/experienceevent-unstructured-content.schema.json— thin field group extending Experience Event, exposingxdm:unstructuredContentvia$ref.components/fieldgroups/experience-event/experienceevent-unstructured-content.example.1.json— example.components/fieldgroups/profile/profile-unstructured-content.schema.json— thin field group extending Individual Profile, exposingxdm:unstructuredContentvia$ref.components/fieldgroups/profile/profile-unstructured-content.example.1.json— example.Validation
npm test— 2429 passing, 1 pendingnpm run lint— cleannpm run validate— 58 failures both before and after this change (pre-existing baseline); zero new failuresnpm run incompatibility-check— cleanBreaking changes
None. Purely additive new data type and field groups.