Sounds good!

Hi @Preeti5  Could you please add some more information or any screenshot to understand the issue a bit more? Thanks!

Hi @bobbym33667819  If you are able to access system/console/bundles please check if any of the bundles are in installed state. Was it working earlier and any recent deployment caused this issue? If not, then I will suggest to go with a fresh install and see if it works or you are still facing the s...

Hi @Kishore_Kumar_  Yes I have integrated AEM with Veeva System which is used for asset management.The assets were uploaded on Veeva instance and it will be synced with multiple AEM instance using a connector code which we developed. Thanks!

Cloud you please add some more information here. I am not clear with the ask. When you say you want to copy paste you want to do it via code? Why is it required as I believe copy paste should be a one time process and can be done manually.

You can build a logic in Java which will iterate through all the pages that you want and will try to retrieve the JSON value. Now convert the JSON to Java Objects and then retrieve whatever information is required from the JSON. Thanks!

Hi @Ronnie09  If you access any of the page with .infinity.json as the extension, you can see the complete page information. Here is a sample:http://localhost:4502/content/we-retail/ca/en/experience.infinity.json Thanks!

Hi @rinaudosal  Please use the below command:mvn -B archetype:generate \-D archetypeGroupId=com.adobe.aem \-D archetypeArtifactId=aem-project-archetype \-D archetypeVersion=27 \-D appTitle="My Multilanguage project" \-D appId="my-project" \-D artifactId="my-project" \-D groupId="com.my.project" \-D ...

On publish instance you will have a replication receiver user which is normally used for replication. Please ensure the correct user and update the permission. It should fix the issue.http://localhost:4503/etc/replication/agents.publish.html 

I see this is only on Author. What about the publish instance? Have you done the same changes on publish instance? It needs to be done on publish as well and the user should be replication receiver I believe. Please check the correct user on publish and adjust the permission.