Hi @markherbalife    You can also look at Asset Share Commons - https://opensource.adobe.com/asset-share-commons/   Thanks Narendra

Hello @datnguyenfiserv    The latest AEM 6.5 Service pack is 6.5.22.  You can download the version and also look at the detailed release notes here - https://experienceleague.adobe.com/en/docs/experience-manager-65/content/release-notes/release-notes   Thanks Narendra

You can look at https://oakutils.appspot.com/generate/index to generate index by providing the queries. I would recommend to proceed with Lucene index as there are multiple properties you are using in queries.

Hi @ASP_Corp    The XMP metadata write back process might have been broken post upgrade. Can you refer this documentation - https://experienceleague.adobe.com/en/docs/experience-manager-65/content/assets/administer/xmp-writeback to confirm if these configurations are in place ?   Thanks Narendra

Hi @dmescia2    Sorry if I am not following this correctly. Content Fragments are stored in AEM under assets - https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/administering/content-fragments/overview   Content Fragments can be managed without sites as well. ...

The GitHub repo link shared above, points to an API - https://html.spec.whatwg.org/multipage/custom-elements.html#custom-elements-api likely your code might be using CustomElements somewhere.   Thanks Narendra

Hi @sreedobe    Please refer the documentation - https://experienceleague.adobe.com/en/docs/experience-manager-learn/foundation/development/understand-indexing-best-practices   If you are trying to get this in AEM as a cloud service environment, you would need to change the index type to Lucene. Hop...

Hi @neo-silicon , it seems you are using https://github.com/ungap/custom-elements this library in your code for custom elements. Once you verify that all the references have been removed from the code, you would be able to remove this reference as well.   Thanks Narendra 

Hi @JayLe12    You can try using the granite:rendercondition for this. I could not find specific examples for assets metadata but the same has been used to control the field visibility in dialogs. Refer this article - https://ankanghosh-webdev.medium.com/granite-render-condition-in-aem-64d32f03a7d1 ...

Hi @aram1995    As OSGi web console is only supported in local SDK and not in cloud environment this may have been removed in the recent releases of Cloud Service. Can you check if you can find any reference to this feature here - https://experienceleague.adobe.com/en/docs/experience-manager-cloud-s...