@AEM_Forum The initializing code should look something like this :   window.adobeDataLayer = window.adobeDataLayer || [];.   More details on setup - https://experienceleague.adobe.com/en/docs/experience-manager-learn/sites/integrations/adobe-client-data-layer/data-layer-overview  

@AEM_Forum  Add the JS that Initializes your data layer object in the root/base page template so that this object is available in all AEM pages.

@manojjain121  Is there a reason why you want to do that? I hope I understood your ask correctly. If all environments are referencing the same asset, any update done to an asset on QA, DEV would reflect on PROD. This would create a lot of confusion for the content authors and your overall asset mana...

@drewcarbory  For Header/footer section, you might want to use an Experience fragment that is then added to your base page template so that the header/footer shows up on all the pages and there is just one place to maintain it (the experience fragment).   As for Mega menu, this needs to be a custom ...

@Johann_Lu  If your client is ok with creating a zip file of the folder structure that you want to upload, you can opt for the extract archive option. https://experienceleague.adobe.com/en/docs/experience-manager-learn/assets/advanced/extract-archive  

@Johann_Lu you can only upload files in AEM DAM from the assets console. However, this might be a possibility with the AEM desktop App (at least to some extent).   https://experienceleague.adobe.com/en/docs/experience-manager-desktop-app/using/archive/best-practices-for-v1  

@SUNITACH1 Just parse this json into a JSON object and then read it accordingly. Once you have the relevant json field, simply use any of the JCR APIs to set these as properties.   Something like this should work for reading the json atleast. I tried with the below mentioned version of org.json libr...

@SUNITACH1  There are 2 POCId fields, one is accessible like topicBody.pocId[0] and the second as topicBody.conceptBody.pocId[0] Which one are you trying to set as property on the metadata node ?

@MaheshMR28  A similar discussion on this topic - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/sightly-in-aem-6-3-org-apache-sling-api-request/m-p/267597  

@MaheshMR28 Can you share your HTL code as well just to see if there is anything that we can spot there?