Dropping Profile Enabled Custom Class Lookup Schema

[itsMeTechy]

Hi All

I have a question regarding the potential impact of removing a Profile Enabled Custom Class Lookup Schema. This schema has an established relationship with another Experience Event schema, which is also profile-enabled.

The plan is to remove the relationship in the Experience Event schema and then drop the Custom Class Lookup dataset and schema. While it seems like a feasible technical action, I’d like to understand if there could be any negative impacts. Since the Custom Class Lookup schema does not participate in the union schema, I assume dropping it won't affect the union schema, but I wanted to double-check with the community.

Looking forward to your insights!

[Devyendar · Accepted solution]

Hi @itsMeTechy 

You can not delete a Schema once it is Profile enabled, I'm assuming you are planning to remove the relationships and delete the Dataset associated to the lookup/custom schema, but the schema itself sticks around (generally I rename the schema with a prefix or suffix 'Archive' to differentiate them)

Lets evaluate the impact of deleting the dataset associated to the lookup schema at multiple levels in AEP, 

1) Union Schema: Separate Union schemas are built for each Type of Schema class that is Individual Record and Experience Event, there is no Union schema built for lookup/custom schema. Hence, no impact here.

2) Segments: Potential impact with any segment that uses the fields of the lookup dataset will break with data no more qualifying.
3) Identity graph: No impact as lookup schema/dataset works at relationship level and not at identity graph level.

In summary, apart from Segments nothing else is supposed to have any impact on AEP-RTCDP.

Regards