How to change the data type of an attribute where schema is enabled for profile and also have a dataset ? which we cannot delete | Community
Skip to main content
B
BellaSnow5378
New Participant
December 29, 2023
Solved

How to change the data type of an attribute where schema is enabled for profile and also have a dataset ? which we cannot delete

  • December 29, 2023
  • 3 replies
  • 1930 views

How to change the data type of an attribute where schema is enabled for profile and also have a dataset ? which we cannot delete

    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 yuhuisg

    Yeah, this is one of the things that I don't like about schemas that are Profile-enabled. I understand and appreciate the limitation, but the restriction is really irritating.

    Let this serve as a reminder to have very detailed names for your fields/field groups, so that you can create new ones that have new meanings/contexts as-and-when required.

    3 replies

    NimashaJain
    NimashaJain
    Employee
    February 6, 2024

    Did you find the suggested solutions helpful? It would be great if you can  mark the answer as correct for posterity. If you have found out solution yourself, share it with wider audience in the community.

    Sneha-Parmar
    Sneha-Parmar
    New Participant
    January 3, 2024

    This is a breaking change and not allowed for Schema that has data and profile enabled. 

      abhinavbalooni
      abhinavbalooni
      New Participant
      December 29, 2023

       Hey @bellasnow5378 

      You would not be able to change the data type of an existing field in a schema enabled for profile and as you mentioned already has a dataset attached to it.

       

      It is a breaking change and would not be allowed.

      You can read more here: https://experienceleague.adobe.com/docs/experience-platform/xdm/schema/composition.html?lang=en

       

      Cheers,

      Abhinav

        yuhuisg
        yuhuisgAccepted solution
        New Participant
        January 2, 2024

        Yeah, this is one of the things that I don't like about schemas that are Profile-enabled. I understand and appreciate the limitation, but the restriction is really irritating.

        Let this serve as a reminder to have very detailed names for your fields/field groups, so that you can create new ones that have new meanings/contexts as-and-when required.

          narendragandhi
          narendragandhi
          New Participant
          January 9, 2024

          Just expanding upon this response. Creating a new field with the desired data type along with a full data load would be the way to go.

            Terms & ConditionsAccessibility statement

            Loading footer...