Skip to main content
Level 2
September 7, 2026
Question

How do you delete a Profile-enabled AEP Individual Profile schema?

  • September 7, 2026
  • 5 replies
  • 64 views

I need to delete two XDM schemas in a development sandbox and I've hit what looks like a closed loop. Hoping someone has been here before.

What I'm trying to do

Some field paths in our dev sandbox differ from prod by character case only - for example campaignUseCase1 in dev versus CampaignUsecase1 in prod. Since XDM field paths are immutable once created, I understand the fix is to rebuild the field group and schemas correctly rather than edit them in place.

Where it breaks

I can't create the correctly-cased fields while the incorrect ones exist, because both paths would land in the same Profile union and AEP rejects paths that differ only by case. So the old objects have to go first.

But:

  1. I can't delete the field group - two schemas compose it.
  2. I can't delete those schemas - both are Profile (union) enabled.
  3. I can't disable Profile in the UI - the toggle is there but Save stays greyed out.
  4. I can't remove the union tag via API. PATCH on the schema with {"op": "remove", "path": "/meta:immutableTags"} returns:
XDM-1501-400  meta:immutableTags Missing"The schema's meta:immutableTags array could not be found. Once this field is added to a schema, it cannot be removed."

Already checked

  • Confirmed both schemas carry meta:immutableTags: ["union"].
  • For one of the two schemas, I deleted its only dataset — zero datasets now reference it, and the schema still won't delete.

Questions

  1. Is there any supported way to remove a schema enabled for profile, or is it genuinely permanent for the life of the schema?
  2. For anyone who has fixed case mismatches between sandboxes - did you go through this, or is there a cleaner approach I should be taking instead?

Sandbox is non-production, so I'm happy to lose the data. It's the schema objects themselves I need gone.

Thanks.

5 replies

Level 1
September 15, 2026
  1. I don’t think there’s a way to delete a profile enabled schema, you can rename the schema to something like ‘do not use’ or ‘deprecated’ so that users don’t use the schema.
  2. Like you said sandbox is non prod and you’re happy to lose all the data then sandbox reset can be an option.

 

You can learn more about sandbox reset here:

https://experienceleague.adobe.com/en/docs/experience-platform/sandbox/ui/user-guide#:~:text=changes%20to%20%E2%80%9CActive%E2%80%9D.-,Reset%20a%20sandbox,-WARNING

Level 2
September 20, 2026

Hi ​@wespy Is there a way like deleting the schema dataset and system dataset for UPS data ( from Adobe Support team? And, then we correct the field path in the existing schema? 

DavidRoss91
Community Advisor
Community Advisor
September 15, 2026

Hello ​@ashexplorer once schema is enabled for profile, you cannot remove it - being it is non prod environment, you’re best course of action is just to mark that schema as unusable

David Ross
Level 2
September 20, 2026

Hi ​@DavidRoss91 Is there a way like deleting the schema linked datasets and system datasets for the profile data ( from Adobe Support team) ? And, then we correct the field path in the existing schema? 

AmitVishwakarma
Community Advisor
Community Advisor
September 21, 2026

Hi ​@ashexplorer Deleting the linked dataset, Profile data, or related system datasets will not unlock the existing Profile-enabled schema. Adobe documents that once a schema is enabled and saved for Real-Time Customer Profile, it cannot be disabled or deleted, and existing fields cannot be removed or renamed. A Profile-enabled dataset can be deleted separately, but that only removes its data/profile records—it does not reverse the schema's Profile enablement. XDM System Troubleshooting Guide · Profile System Jobs API Endpoint https://experienceleague.adobe.com/en/docs/experience-platform/xdm/troubleshooting-guide https://experienceleague.adobe.com/en/docs/experience-platform/profile/api/profile-system-jobs

Therefore, Adobe Support cannot use dataset/system-dataset deletion as a supported way to correct the field-path casing in the same existing schema. System datasets should not be manually deleted as a workaround.

Recommended approach

Because this is a development sandbox and the data can be discarded:

  1. Reset the sandbox and recreate the field group/schema with the correct casing before enabling Profile. A sandbox reset removes the sandbox resources, including schemas and datasets, while retaining the sandbox name and permissions. https://experienceleague.adobe.com/en/docs/experience-platform/sandbox/ui/user-guide
  2. If reset is not possible, create a new development sandbox and rebuild/migrate the schema there.
  3. In the existing sandbox, rename the old schema to Deprecated or Do Not Use and stop ingesting into it. https://experienceleague.adobe.com/en/docs/experience-platform/xdm/troubleshooting-guide

Also, creating another field that differs only by uppercase/lowercase is not a reliable workaround because XDM treats the field path as already existing. A case-only correction must be done by rebuilding the affected schema in a clean/reset environment; it cannot be fixed in place after Profile enablement. https://experienceleague.adobe.com/en/docs/experience-platform/xdm/schema/composition

Amit Vishwakarma - Adobe Commerce Champion 2025 | 17x Adobe certified | 6x Adobe SME