Expand my Community achievements bar.

SOLVED

Having problem in creating custom metadata.

Avatar

Level 2

Hi,

 

I am using AEM 6.5. I want to configure custom meta data to create additional tab in asset properties. I have a package containing the details of metadata. I am facing problem in installing the package. I also want to highlight that there is no default metadataschema present in /conf/global/settings/dam/adminui-extension/metadataschema. I am facing error following error in installing the package. 

hs06_0-1624949886233.png

Please help to resolve the issue.

 

Thank you

 

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Hi @hs06!

This error message usually indicates an issue with the content structure of your package.

Most probably you are missing resource types on one or multiple levels of the hierarchy (resulting in defaults being applied) or you have set wrong resource types in your .content.xml files.

Please make sure that the content structure of your package has all relevant resource types set/defined and that you are following the given constraints.

Please check that the sub-nodes below the defined "sling:Folder" reflect resource types that are allowed for this location.

You may also want to check the existing structure in your JCR repository. If there are wrong resource types present you may want to delete the structure that's covered by your package before attempting a new deployment of your fixed package.

 

Hope that helps!

 

View solution in original post

3 Replies

Avatar

Correct answer by
Employee Advisor

Hi @hs06!

This error message usually indicates an issue with the content structure of your package.

Most probably you are missing resource types on one or multiple levels of the hierarchy (resulting in defaults being applied) or you have set wrong resource types in your .content.xml files.

Please make sure that the content structure of your package has all relevant resource types set/defined and that you are following the given constraints.

Please check that the sub-nodes below the defined "sling:Folder" reflect resource types that are allowed for this location.

You may also want to check the existing structure in your JCR repository. If there are wrong resource types present you may want to delete the structure that's covered by your package before attempting a new deployment of your fixed package.

 

Hope that helps!

 

Avatar

Community Advisor

Hi,

Try to create thses folders as sling:OrderedFolder

/conf/global/settings/dam/adminui-extension

/conf/global/settings/dam/adminui-extension/metadataschema



Arun Patidar