How to remove required field in XDM Schema

Forum|Forum|23 days ago
January 21, 2026
5 replies
76 views

Is there a way to uncheck the ‘required’ in a xdm schema for a field after it is created and saved?

Schemas

Best answer by Tof_Jossic

@jane_12

For your own custom fields, removing the ‘required’ option should be supported but some other standard fields are locked (greyed out).

If this is a primary identity field, that would be required by definition so you’d have to change that but once data has been ingested (or the schema is used in Profile), changing that identity designation is treated as a breaking change and would be blocked.

Can you maybe provide more details or a screenshot?

Tof_Jossic

Accepted solution

Adobe Employee

@jane_12

For your own custom fields, removing the ‘required’ option should be supported but some other standard fields are locked (greyed out).

If this is a primary identity field, that would be required by definition so you’d have to change that but once data has been ingested (or the schema is used in Profile), changing that identity designation is treated as a breaking change and would be blocked.

Can you maybe provide more details or a screenshot?

A

Abie

Level 4

Hi @jane_12 ,

The answer indeed depends on what sort of field are you referring to? A field from OOTB field group, custom field, identity type, relation type et cetera.

Thanks!

S

SG14_97

Level 2

It depends on nature - OOTB or custom attributes defined for the XDM but also note sometimes OOTB attributes/field groups even though appear to be required are not mandated to fill in.

For your question - If it is custom it can be removed(given that its not primary identity and no profile ingestion has already happened else breaking change), for OOTB identity or required field in most cases its locked (however exception here are there like the OOTB privacy and consent field group if added all fields are marked required while in practice it depends on what data you load and ingestion is not blocked).

bjoern__koth

Community Advisor and Adobe Champion

To add on what @Tof_Jossic said,

removing the “required” setting is not considered a breaking change
making a previously optional field required, however, is a breaking change due to the then missing data on previously ingested data

Cheers from Switzerland!

J

jane_12Author

Level 3

Providing screenshots for reference