"$id" vs. "meta:altId" when creating datasets | Community
Skip to main content
DavidRoss91
Community Advisor
DavidRoss91Community Advisor
Community Advisor
December 22, 2023
Solved

"$id" vs. "meta:altId" when creating datasets

  • December 22, 2023
  • 2 replies
  • 1208 views

Hello – When creating a dataSet via Postman API’s, I inadvertently used the “meta:altId” value, instead of “$id” value to reference back to the schema.

 

I attempted to make a PATCH request to update the schemaRef, but response is returning as forbidden. Does using the “meta:altId” cause any issues in the long run? The data ingestion process using that dataSet and schema appear to actually be working just fine, so this is just a concern of any long term affects. 

 

I do realize that I can delete the dataSet and re-create, but trying to avoid that if at all possible.

    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 abhinavbalooni

    Hey @davidross91 

     

    As per my understanding, since we always have a dataset based on a schema. I don't think it will be a challenge. Might well just be a UI querk which many might not have noticed just yet cause not a lot of folks go with altId. Also, any approach that works would work for long term as well. I might be wrong but that's my understanding.

    2 replies

    abhinavbalooni
    Community Advisor
    abhinavbalooniCommunity Advisor
    Community Advisor
    December 22, 2023

    Hey @davidross91 

     

    You can use either of the two: $id or meta:altId. Both are mentioned in the documentation and either can be used.

     

    Official link to the documentation: https://experienceleague.adobe.com/docs/experience-platform/xdm/api/schemas.html

      DavidRoss91
      Community Advisor
      DavidRoss91Community AdvisorAuthor
      Community Advisor
      December 22, 2023

      Hi, thanks for the quick reply. I did see that also in the documentation but I believe that was in the schema not dataset documents. 

       

      Also, I did some testing in a development sandbox using the "$id" and also "meta:altId" and noticed that when using the "$id" value, the UI will show that the schema has a dataset linked to it. But, when you use the "meta:altId" it does not. That is what sparked this concern. I have attached a screen grab below. Now I will say, that when you click into the dataSet, it does show the schema being used. This is my only concern here.

       

        abhinavbalooni
        Community Advisor
        abhinavbalooniCommunity AdvisorAccepted solution
        Community Advisor
        December 22, 2023

        Hey @davidross91 

         

        As per my understanding, since we always have a dataset based on a schema. I don't think it will be a challenge. Might well just be a UI querk which many might not have noticed just yet cause not a lot of folks go with altId. Also, any approach that works would work for long term as well. I might be wrong but that's my understanding.

          NimashaJain
          Adobe Employee
          NimashaJainAdobe Employee
          Adobe Employee
          January 16, 2024

          @davidross91 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.

          Terms & ConditionsAccessibility statement

          Loading footer...