Remove field vs Deprecate field | Community
Skip to main content
EricD206
EricD206
New Member
October 21, 2025
Solved

Remove field vs Deprecate field

  • October 21, 2025
  • 1 reply
  • 328 views

I have 2 scheme elements under our base field group.
queryString has the 'Deprecate field' option.
queryStringRedacted as the 'Remove field' option.

I do not believe any data has ever been ingested for the queryStringRedacted element.
I need to change the name.
Can I remove it or rename it without creating a breaking change for the datasets tied to it?

If I can't remove it, do I use the 'Manage related fields' to hide it from the UI?

    Best answer by bjoern__koth

    Hi @ericd206 

    in general, schemas only allow additive modifications and removing field is not possible unless the field has never received data like in your case (lucky you!).

    That's why once data has been received for that field, you can only deprecate it which essentially hides it from view like for instance segmentation.

    Important to understand is that deprecating a field will not delete previously ingested data.

    1 reply

    bjoern__koth
    Community Advisor and Adobe Champion
    bjoern__kothCommunity Advisor and Adobe ChampionAccepted solution
    Community Advisor and Adobe Champion
    October 21, 2025

    Hi @ericd206 

    in general, schemas only allow additive modifications and removing field is not possible unless the field has never received data like in your case (lucky you!).

    That's why once data has been received for that field, you can only deprecate it which essentially hides it from view like for instance segmentation.

    Important to understand is that deprecating a field will not delete previously ingested data.

    Cheers from Switzerland!
      Terms & ConditionsAccessibility statement

      Loading footer...