What should be the URI to be added while creating the name space? I tried with my author instance URI with the DAM path and setted up the namesapce. But it isn't working. Am I missing something here?

There is no overlays done on Card view that I'm aware of. I can add files to AEM DAM folders using the classic UI at localhost:4502/damadmin.The AEM version I'm using is AEM 6.5.10.The error log says, com.day.cq.dam.commons.metadata.SimpleXmpToJcrMetadataBuilder Unable to extract the complex metadat...

Thanks for your response. However I'm looking to understand what would be expected target behavior for the scenario I've mentioned.

Thanks @arunpatidar One question here would be, in the documentation it is showing list v2. Any thoughts on this?

Thanks for your response. However, this is not what I'm looking for.I'm on AEM 6.5.10 and the core component version I'm is 2.7.0. I'm not seeing the additional option in the list core component cq:dialog to enable the teaser option. When I check the component documentation it is part of list v2, an...

Hi @Gaureshk_Kodag The changes are direct HTML changes, not using any loops or intervals. The target call is only getting fired once.The issue is not persistent always, it appears intermittently. With the mboxtrace no issues were observed. 

Thanks @arunpatidar I tried this, however we needed to define fixed width/height for crop rather than the ratios. And it was achieved using the image profiles and smart crop option, which enabled us to define fixed image dimensions for crop as "image profiles" and using "smart crop" to crop the asse...

Hi @CJara1 You can make use of profile parameters to pull the datalayer value into target.  Reference: https://experienceleaguecommunities.adobe.com/t5/adobe-target-questions/odd-issues-with-profile-parameters/m-p/427214#M7068Once you have the datalayer variable in target you can use it in the offer...

@Siva_Sogalapalli ACS Commons asset importer can't be used to update metadata as the purpose of the tool is to import assets. Feel free to correct me if I'm wrong. And also I needed to have this done for existing assets in DAM.

Thanks @lukasz-m Another solution I tried was creating a package of all the metadata nodes under a path, and then update the xml by emptying the dc:description(done using VS Code searching all occurances under the folder), repackaging and installing it.