Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Having problem in creating custom metadata.

Avatar

Avatar
Boost 1
Level 1
hs06
Level 1

Likes

2 likes

Total Posts

11 posts

Correct Reply

0 solutions
Top badges earned
Boost 1
Give Back
Ignite 1
Validate 1
View profile

Avatar
Boost 1
Level 1
hs06
Level 1

Likes

2 likes

Total Posts

11 posts

Correct Reply

0 solutions
Top badges earned
Boost 1
Give Back
Ignite 1
Validate 1
View profile
hs06
Level 1

28-06-2021

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

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Affirm 50
Employee
markus_bulla_adobe
Employee

Likes

138 likes

Total Posts

121 posts

Correct Reply

59 solutions
Top badges earned
Affirm 50
Boost 100
Applaud 25
Affirm 25
Boost 50
View profile

Avatar
Affirm 50
Employee
markus_bulla_adobe
Employee

Likes

138 likes

Total Posts

121 posts

Correct Reply

59 solutions
Top badges earned
Affirm 50
Boost 100
Applaud 25
Affirm 25
Boost 50
View profile
markus_bulla_adobe
Employee

29-06-2021

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!

 

Answers (2)

Answers (2)

Avatar

Avatar
Contributor
Level 4
Bimmi_Soi
Level 4

Likes

68 likes

Total Posts

74 posts

Correct Reply

24 solutions
Top badges earned
Contributor
Applaud 5
Boost 50
Ignite 1
Affirm 10
View profile

Avatar
Contributor
Level 4
Bimmi_Soi
Level 4

Likes

68 likes

Total Posts

74 posts

Correct Reply

24 solutions
Top badges earned
Contributor
Applaud 5
Boost 50
Ignite 1
Affirm 10
View profile
Bimmi_Soi
Level 4

29-06-2021

Avatar

Avatar
Coach
MVP
Arun_Patidar
MVP

Likes

1,428 likes

Total Posts

3,300 posts

Correct Reply

937 solutions
Top badges earned
Coach
Contributor 2
Ignite 10
Give Back 700
Boost 1000
View profile

Avatar
Coach
MVP
Arun_Patidar
MVP

Likes

1,428 likes

Total Posts

3,300 posts

Correct Reply

937 solutions
Top badges earned
Coach
Contributor 2
Ignite 10
Give Back 700
Boost 1000
View profile
Arun_Patidar
MVP

30-06-2021

Hi,

Try to create thses folders as sling:OrderedFolder

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

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