Asset Metadata custom properties name getting changed while moving content from one environment to another | Community
Skip to main content
R
ReddyIshanvi
Level 3
June 8, 2023
Solved

Asset Metadata custom properties name getting changed while moving content from one environment to another

  • June 8, 2023
  • 2 replies
  • 776 views

We have created (and registered)  a custom namespace "test" and custom metadata schema and properties. All the assets on dev environment have properties like "test:brand" and everything is working as expected but when I am moving the content from one environment to another, property name is getting changed from "test:brand" to "test0:brand".

I verified the content.xml before uploading the content and the property name is "test:brand" but it's getting changed to "test0" when we are importing the content on another environment . Also an additional property "testt0:brand_xmpArray" with value "rdf:Bag" is getting generated. I tried changing the property name by downloading the content package from the environment where it’s getting changed and changed the property name from "test0:brand" to "test:brand" and tried uploading the package but I am getting the below error and metadata is getting deleted for the assets.

 
E /content/dam/test/content/reports/Report.pdf (org.xml.sax.SAXParseException; systemId: file:///data/aem/author/jcr_root/content/dam/test/content/reports/Report.pdf/.content.xml; lineNumber: 66; columnNumber: 75; The prefix "test" for attribute "test:brand" associated with an element type "metadata" is not bound.
 
Any ideas why this is happening and how to fix this issue?
 
Properties are getting generated with the correct name when we are creating the asset and adding the metadata on the same environment. We are having issues when we are importing the assets from dev environment to another Please advise.
 

 

 

 

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 EstebanBustamante

How you are moving/creating the "test" namespace in the upper environment? It sounds to me that you are adding once more the "test" namespace while migrating your assets to the upper environment.

If so, you may have a conflict with the namespaces in the upper environment, can you verify that the namespaces are correctly created and not duplicated? You can check here: http://localhost:4502/crx/de/index.jsp#/jcr%3Asystem/rep%3Anamespaces

2 replies

EstebanBustamante
Community Advisor and Adobe Champion
EstebanBustamanteCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
June 8, 2023

How you are moving/creating the "test" namespace in the upper environment? It sounds to me that you are adding once more the "test" namespace while migrating your assets to the upper environment.

If so, you may have a conflict with the namespaces in the upper environment, can you verify that the namespaces are correctly created and not duplicated? You can check here: http://localhost:4502/crx/de/index.jsp#/jcr%3Asystem/rep%3Anamespaces

Esteban Bustamante
    ManviSharma
    Adobe Employee
    ManviSharmaAdobe Employee
    Adobe Employee
    June 9, 2023

    Hi,

     

    The issue of property name changing from "test:brand" to "test0:brand" during content migration between environments could be related to namespace conflicts. Check the namespace registration and configuration in the destination environment to ensure it matches the source environment.

     

    Additionally, verify that the custom namespace "test" and associated metadata schema are correctly configured in both environments to maintain consistency.

      Terms & ConditionsAccessibility statement

      Loading footer...