Hi,  Are you sure MetaData Profiles does not meet your needs  https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/manage/metadata-profiles ?. Perhaps is easier to customize the Asset Share Commons components than implement the custom "cascading metadata". Howev...

Hi,  There are multiple ways to achieve what you are trying to do. I would suggest discarding the query approach and instead using a Workflow Launcher that triggers a Workflow upon a new asset being added or created. This will initiate a custom workflow that provides you with the asset path, allowin...

Hi,    There is no official guide to migrate from SPA archetypes to Vite. Technically, I think it is possible; however, some things are pre-configured to run smoothly with Webpack. For example, the manifest.json that SPA relies on is set and easy to configure in Webpack, whereas in Vite, you need to...

Hi, The SPA components will render in the SPA Editor, and the AEM WCM Core component will render in the Page Editor, which are 2 different technologies, that share the same UI, but these are not compatible, you can read more here:  https://experienceleague.adobe.com/en/docs/experience-manager-65/con...

Hi,  These are my two cents, and please take them as my personal advice. First of all, while the number may look scary, I'm sure many of those instances will be the same mistake repeated. I think diving deep into the report might give you a better idea of the actual workload. Now, addressing your qu...

Hi @Nirmal_Kumar1 @Nandheswara whenever you make a change in the index's definition, you must reindex the index, otherwise, changes won't take effect. Answering your questions:   The "reindex" property automatically returns to "false" once the indexing process is finished. The damLucene index is a...

Hi, I don't know off the top of my head, but could you please try if any of these work? Here's the link: https://developer.adobe.com/experience-cloud/experience-manager-apis/. These are all the available APIs for Assets for now, so if none work, I think you will get an answer.

Hi,   You cannot achieve that with the out-of-the-box (OOTB) pathfield functionality. However, you have several options: Add a validator that prevents the selection of child pages and shows an error message. Check here: https://lucanerlich.com/docs/aem/dialog-validation/ https://aemlab.blogspot.com...

Hi,    This feature is intended for you to have a way to "deeplink" into a specific tab or slide [1]. So, removing this functionality would require updating the JavaScript responsible for updating the URL. I believe you would need to change this file: https://github.com/adobe/aem-core-w...

Oh, I see. Then, you should check the navigation component from SPA - Angular project, here you have: https://experienceleague.adobe.com/en/docs/experience-manager-learn/getting-started-with-aem-headless/spa-editor/angular/navigation-routing and the code https://github.com/adobe/aem-guides-wknd-spa/...