Hi @ksuayan_shc, According to AEM.6.5.14 release notes: https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/release-notes.html?lang=en#uber-jar There is no dedicated uber jar for AEM 6.5.14 and you should use 6.5.13 uber jar.

Hi @malay_dube, It's not possible to have file upload in asset metadata schema without customization. Nevertheless this seems to be incorrect usage of metadata schema, it has not been designed for file upload. https://experienceleague.adobe.com/docs/experience-manager-65/assets/administer/metadata-s...

Hi @spidey1405, In general, it looks some information are missing in your JSON, e.g. cq:model property which is mandatory. Please have a look under below documentation: AEM Assets API in context of CF - https://experienceleague.adobe.com/docs/experience-manager-65/assets/extending/assets-api-content...

Hi @spidey1405, Search and sorting are not supported by AEM Assets API. I think that general purpose of AEM Assets API is a bit different than what you would like to achieve. It has been designed to manage assets and run CRUD operation instead of search/filtering etc. All the details you can find un...

Hi @spidey1405, If by path you mean path to each node that is included in result you can use jcr:path as a property, so your query will look like this: type=nt:unstructured path=/content/dam/wknd-shared/en/adventures nodename=master p.hits=selective p.properties=tripLength jcr:path and the results: ...

Hi @vjleo94, I think this is happening only when you will set shallow parameter to true. In that case only jcr:content will be removed, and cq:Page node will remain (at least this is how it works on AEM 6.5.12) The path that delete method is using is a path to cq:Page. So this is why you see Activat...

Hi @spidey1405, I think that the simplest option, will be to use relative path the parent node from which you would like to read property values. Assuming you wanted to use cq:model property value that is stored under data node, and get all master variation, you can try something like that. type=nt:...

Hi @spidey1405, If I good understand your case, you would like to get only master variation of content fragment. Assuming that master variation is stored under master node, you can consider to use nodename predicate: https://experienceleague.adobe.com/docs/experience-manager-65/developing/platform/q...

Hi @spidey1405, In general contentFragment predicate checks, if there is a contentFragment property with true value, located under jcr:content node. Base on that contentFragment predicate decides if given resource is recognized as content fragment or not and if it should be included in the results. ...

Hi @huy39382677 , According to the documentation: https://experienceleague.adobe.com/docs/experience-manager-65/assets/extending/graphql-api-content-fragments.html?lang=en#helper-fields to retrieve date values from metadata you can use calendarMetadata or calendarArrayMetadata, something like this: ...