I am following the documentation https://experienceleague.adobe.com/en/docs/platform-learn/implement-web-sdk/tags-configuration/creat... 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
{"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
Solved! Go to Solution.
Views
Replies
Total Likes
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.
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.
Can you please confirm the sandbox(s) have been mapped into the Adobe Web SDK extension?
Its already configured and mapped, its only the problem with two data element type
variable and xdm object rest of the data element works fine
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
@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!
Views
Replies
Total Likes
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.
Views
Like
Replies