Not able to search assets based on exact values of custom metadata fields. | Community
Skip to main content
Level 2
April 22, 2024
Solved

Not able to search assets based on exact values of custom metadata fields.

  • April 22, 2024
  • 4 replies
  • 1186 views

In AEM DAM, we can search assets based on exact values of metadata fields, such as, title, description, and creator. For example, title:John

 

Same way when we search for a user-generated/custom property, with its field label in the property editor in lowercase, with spaces removed then we are getting error as shown in attachment.

 

Also, we are not able to search assets based on metadata fields in Brand Portal as well. (for custom and default fields both)

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 Adilos-Cantuerk

Have you tried to create a custom search filter in the admin assets search rail?
Maybe there is a typo or the custom property is not located in the metadata?
From what I have seen is, that you are able to create custom properties directly in jcr:content/ but those are not automaticaly added to the index.
If you create your custom property in jcr:content/metadata, this should work - and you can quickly check with a custom search filter.

4 replies

Adilos-Cantuerk
Community Advisor
Adilos-CantuerkCommunity AdvisorAccepted solution
Community Advisor
April 23, 2024

Have you tried to create a custom search filter in the admin assets search rail?
Maybe there is a typo or the custom property is not located in the metadata?
From what I have seen is, that you are able to create custom properties directly in jcr:content/ but those are not automaticaly added to the index.
If you create your custom property in jcr:content/metadata, this should work - and you can quickly check with a custom search filter.

David_Fischer92
Level 3
April 23, 2024

One additional note is that for Brand Portal, you are unable to add an index for a custom field if it starts with xmp.  We were able to get it added by reaching out to Adobe Support but it took some time.

abhishekanand_
Community Advisor
Community Advisor
April 30, 2024

When dealing with user-generated or custom properties, ensure the following:
The field label in the property editor should match the actual metadata field name.
If the field label contains spaces, use underscores or camel case to represent the field name.
Ensure that the field name is correctly mapped to the metadata property in AEM.

Unfortunately, Brand Portal does not support searching assets based on custom metadata fields directly.
However, you can leverage smart collections and filters to organize and retrieve assets effectively within Brand Portal

Abhishek Anand
diksha_mishra
Community Advisor
Community Advisor
May 7, 2024

@anurag_dang Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

kautuk_sahni
Community Manager
Community Manager
May 16, 2024

@anurag_dang Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

Kautuk Sahni