modeling subscription in XDM -> use XDM Individual or custom class | Community
Skip to main content
Michael_Soprano
Michael_Soprano
Level 10
May 25, 2025
Solved

modeling subscription in XDM -> use XDM Individual or custom class

  • May 25, 2025
  • 1 reply
  • 334 views

I have got project for telco company. The user might have multiple subscriptions. We are still in the discovery phase. 

I see that subscriptions might be included in the Data Model in two following ways. 

1. XDM Individual Profile Class + Subscription Data Type 

Pros:

It would be included in RTCP

 

However when I tried to model something like that I got the error:

Do you know what it might be about???

 

2. Custom Subscription Class + Subscription Data Type 

Pros: 

Might be more customizable? 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Asheesh_Pandey

@michael_soprano There may be many other ways to address your use case. I'll focus on the specific questions you asked.

1. This error generally appears when user try to define fields at the root level, Instead they should extending XDM class "XDM individual profile" and field groups, using the allOf structure.

Steps to fix : a. Select standard class >> b. Add default field groups (Like identity) OR Add custom field groups >>  c. add custom field

Note: Do not add field directly at the root, this will let AEP manage fields through filed group and classes.

2. Custom class is useful to define unique structure specific to your org that don't fit into standard XDM. Important to note that to use custom class data in RTCDP, you will likely need to establish relationship (transform and Join) with standard schemas (e.g. XDM individual profile).
2 Cents: Consider using standard classes and filed groups where it is possible, as this ensure better compatibility and ease of use with RTCDP.

1 reply

Asheesh_Pandey
Community Advisor
Asheesh_PandeyCommunity AdvisorAccepted solution
Community Advisor
May 25, 2025

@michael_soprano There may be many other ways to address your use case. I'll focus on the specific questions you asked.

1. This error generally appears when user try to define fields at the root level, Instead they should extending XDM class "XDM individual profile" and field groups, using the allOf structure.

Steps to fix : a. Select standard class >> b. Add default field groups (Like identity) OR Add custom field groups >>  c. add custom field

Note: Do not add field directly at the root, this will let AEP manage fields through filed group and classes.

2. Custom class is useful to define unique structure specific to your org that don't fit into standard XDM. Important to note that to use custom class data in RTCDP, you will likely need to establish relationship (transform and Join) with standard schemas (e.g. XDM individual profile).
2 Cents: Consider using standard classes and filed groups where it is possible, as this ensure better compatibility and ease of use with RTCDP.

- Asheesh
    Terms & ConditionsAccessibility statement

    Loading footer...