Metadata Fields Have Vanished | Community
Skip to main content
Erika_Antkowiak
Erika_Antkowiak
Level 4
January 14, 2025
Solved

Metadata Fields Have Vanished

  • January 14, 2025
  • 4 replies
  • 770 views

Hi friends, 

 

Has anyone experienced metadata fields disappearing from their AEM Assets? They populate in Content Hub, but are no longer in AEM Assets. It looks like our ability to edit metadata schemas has been removed as well. We just had this happen to us and are attempting to get it remediated, but wanted to reach out to see if this has happened to anyone else. Thanks in advance for your responses!

 

Best,

E

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 Erika_Antkowiak

Hi team, 

 

I wanted to share an update on this issue. It turns out that renaming a product profile within the Adobe Admin Console was the cause of our metadata and permissions problem. Thankfully, we keep the original product profile naming saved somewhere safe just in case. When we copy and pasted the original product profile names back into the Adobe Admin Console all metadata was visible again and we were able to pull reports, move assets, etc. I'm happy to help anyone who experiences a similar issue. All is well with our instance for now.

 

Best,

E

4 replies

gkalyan
Community Advisor and Adobe Champion
gkalyanCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
January 15, 2025

@erika_antkowiak 

can you specify which version? Also, is this happening after a migration?

If you can let us know when it started happening?

    SreenivasBr
    SreenivasBr
    Level 4
    January 17, 2025

    This might happen if the metadata schema is deployed through code and it is overwriting the existing metadata schema in AEM Assets. Did this issue happen after code deployment? If yes, then the above might be the case.

      narendiran_ravi
      narendiran_ravi
      Level 6
      January 18, 2025

      Hi @erika_antkowiak ,

      To check if the custom metadata schema is present and troubleshoot potential issues:

      1. Verify the CRX Path:
        Check if the custom metadata schema exists at the following path:
        /conf/global/settings/dam/adminui-extension/metadataschema.

      2. Check for Code Overrides:
        There is a chance this schema might have been overridden through recent code changes. Verify if any recent updates were made in the code that impact this path.

      3. Review the filter.xml:
        Check the filter.xml file in the codebase to see if this path is included in the filter. If it is included, it might have caused the metadata schema to be overwritten during deployment.

        Erika_Antkowiak
        Erika_AntkowiakAuthorAccepted solution
        Level 4
        January 28, 2025

        Hi team, 

         

        I wanted to share an update on this issue. It turns out that renaming a product profile within the Adobe Admin Console was the cause of our metadata and permissions problem. Thankfully, we keep the original product profile naming saved somewhere safe just in case. When we copy and pasted the original product profile names back into the Adobe Admin Console all metadata was visible again and we were able to pull reports, move assets, etc. I'm happy to help anyone who experiences a similar issue. All is well with our instance for now.

         

        Best,

        E

        Terms & ConditionsAccessibility statement

        Loading footer...