Create data element error with variable selection | Community
Skip to main content
M
Community Advisor
MshajiCommunity Advisor
Community Advisor
September 28, 2024
Solved

Create data element error with variable selection

  • September 28, 2024
  • 2 replies
  • 1518 views

I am following the documentation https://experienceleague.adobe.com/en/docs/platform-learn/implement-web-sdk/tags-configuration/create-data-elements to create data element.
In the section Create Variable data elements for XDM and data objects when I select variable at step 4, I get error message
An error occurred.
Failed to load schema metadata. The resource was not found.
when I debugged it using chrome developer tools I found
http://ns.adobe.com/aep/errors/XDM-2012-404
A sandbox with the name undefined is not found. Error from Sandbox Management API: The sandbox was not found. 

I get the same issue when looked at the network call I see


https://platform.adobe.io/data/foundation/schemaregistry/tenant/schemas?property=meta:class==https%3...

 

{"type":"http://ns.adobe.com/aep/errors/XDM-2012-404","title":"Sandbox not found","status":404,"report":{"registryRequestId":"8147b086-1e1d-41be-8ddf-9975a3b27825","timestamp":"09-27-2024 11:41:32","detailed-message":"A sandbox with the name undefined is not found. Error from Sandbox Management API: The sandbox was not found. Refresh the page and try again.","sub-errors":[]},"detail":"A sandbox with the name undefined is not found. Error from Sandbox Management API: The sandbox was not found. Refresh the page and try again."}

I tried in incognito and different browsers, problem remains same in all browsers.

http://ns.adobe.com/aep/errors/XDM-2012-404 is something adobe internal url not accessible to public. Not sure what this means, if anyone experienced this pls let me know how to resolve this.

Attaching screenshot and video

 

 

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 Mshaji

Yes that is correct, however it doesn't resolve the issue. This seems to be a product bug, not sure if there is any workaround

 

Here is the response from adobe engineer

We've added those sandboxes. That's why I think it's an actual product bug (or they intentionally require admin permissions for some reason). As an admin, I can access the dropdown but it seems like anyone with access to those sandboxes should be able access them as well.

 

 

 

We've added those sandboxes. That's why I think it's an actual product bug (or they intentionally require admin permissions for some reason). As an admin, I can access the dropdown but it seems like anyone with access to those sandboxes should be able access them as well.

 

2 replies

brekrut
Adobe Employee
brekrutAdobe Employee
Adobe Employee
September 28, 2024

Hello @mshaji 

 

When using the Adobe Web SDK within Adobe Launch/data collection there is a configuration which maps the Web SDK extension to a sandbox.  Please refer to this article.

 

https://experienceleague.adobe.com/en/docs/experience-platform/tags/extensions/client/web-sdk/web-sdk-extension-configuration#datastreams

 

Can you please confirm the sandbox(s) have been mapped into the Adobe Web SDK extension?

    M
    Community Advisor
    MshajiCommunity AdvisorAuthor
    Community Advisor
    September 29, 2024

    Hi @brekrut ,

    I compared xhr calls between dev and prod sandbox, I recorded their request and response, u can see the difference in call for x-sandbox-name

    It seems that on dev x-sandbox-name is passed as undefined in request header. 
    It says When making calls to Experience Platform APIs, a sandbox name must be supplied under the header x-sandbox-name
     
    Why x-sandbox-name is not being passed  in dev sandbox? are there any settings to passing sandbox-name
     
    Dev sandbox
     
    XHRGET
    [HTTP/1.1 404 Not Found 122ms]
     
    GET /data/foundation/schemaregistry/tenant/schemas?property=meta%3Aclass%3D%3Dhttps%253A%252F%252Fns.adobe.com%252Fxdm%252Fcontext%252Fexperienceevent HTTP/1.1
    Host: platform.adobe.io
     
    x-api-key: Activation-DTM
    x-gw-ims-org-id: xxxxxxxx@AdobeOrg
    Authorization: Bearer xxxx
    Content-Type: application/json
    x-sandbox-name: undefined
     
     
    {"type":"http://ns.adobe.com/aep/errors/XDM-2012-404","title":"Sandbox not found","status":404,
    "report":{"registryRequestId":"541b994b-b07d-435c-9a88-998eebd55496","timestamp":"09-28-2024 11:57:18",
    "detailed-message":"A sandbox with the name undefined is not found. Error from Sandbox Management API: The sandbox was not found. Refresh the page and try again.","sub-errors":[]},"detail":"A sandbox with the name undefined is not found. Error from Sandbox Management API: The sandbox was not found. Refresh the page and try again."}
     
     
    Prod sandbox
     
     
    GET /data/foundation/schemaregistry/tenant/schemas?property=meta%3Aclass%3D%3Dhttps%253A%252F%252Fns.adobe.com%252Fxdm%252Fcontext%252Fexperienceevent HTTP/1.1
    Host: platform.adobe.io
     
    x-api-key: Activation-DTM
    x-gw-ims-org-id: xxxxxx@AdobeOrg
    Authorization: Bearer xxxxx
    Content-Type: application/json
    x-sandbox-name: prod
     
    XHRGET
    [HTTP/1.1 200 OK 174ms]
     
    {"results":[{"$id”:…...,"title":"WKND Demo Website AA Data Collection”},…..}
      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      October 18, 2024

      @mshaji Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

      Kautuk Sahni
      M
      Community Advisor
      MshajiCommunity AdvisorAuthorAccepted solution
      Community Advisor
      October 18, 2024

      Yes that is correct, however it doesn't resolve the issue. This seems to be a product bug, not sure if there is any workaround

       

      Here is the response from adobe engineer

      We've added those sandboxes. That's why I think it's an actual product bug (or they intentionally require admin permissions for some reason). As an admin, I can access the dropdown but it seems like anyone with access to those sandboxes should be able access them as well.

       

       

       

      We've added those sandboxes. That's why I think it's an actual product bug (or they intentionally require admin permissions for some reason). As an admin, I can access the dropdown but it seems like anyone with access to those sandboxes should be able access them as well.

       

        Terms & ConditionsAccessibility statement

        Loading footer...