@jezwn not really i tried different approaches as well but nothing seems to be perfect, for this i have also share an idea of integration here's the link to it https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-ideas/proposal-for-integration-between-aem-dam-and-aec-assets/idi-...

Hi @nithya90  As @arunpatidar suggested you can use the AssetVersionManager to fetch the version number and that's a ideal way as well below is a code snippet which might help you:  Resource assetResource = resourceResolver.getResource(assetPath); Asset asset = assetResource.adaptTo(Asset.cla...

Hi @Nimma05  These exceptions suggests that exceptions you’re encountering when using PageManager.delete() in AEM are related to issues with the page’s versioning, permissions ensure that the page is not involved in any active workflows. Workflow references can sometimes prevent page deletion. what ...

Hi @digarg17 Short Answer yes it is supported in ASC i did a POC for a client some months back.but you need to search the a complete text which is being mentioned in file for instance lets say "Abhishek" is there in the file it won't result until i search "Abhishek" not a single character should be ...

Hi @SHIBANI06  There could be several factors contributing to the error. To accurately identify the RCA, I'd need to review the error logs for more specific information.Please let me know if you can provide those details

Hi @NickAd1 Below is a demo servlet which you can use to get the replication status of any content passed through parameters like : http://localhost:4502/bin/checkReplicationStatus?path=/content/dam/myProject/image.jpg import com.day.cq.replication.ReplicationStatus; import com.google.gson.JsonObjec...

As @MukeshYadav_ you need to check the value represent the root category id in Magento store it can be "Mg==" or "Mw==" try with these two values and also in your configuration remove the default http headers and also check the advanced tab configuration GraphQL Proxy Path * and also check Enable Ca...

can you check your port number in pom and what is the port that your instance is running on, they should be similar  i can see that in your pom it's 4502 which means your instance must be running on something else check that it should be http://localhost:4502/ or check 4502 value in parent pom to th...

as @Sady_Rifat mentioned try to run the unit test individually or you can skip the test cases as well using below commandmvn clean install -PautoInstallPackage -DskipTests