Hi, You can click on the "Emulator" button while editing the page. This will hide the contexthub and you should be able to add the componnets from left pane.    I have also  noticed the same in RDE. May be some issue if contexthub is enabled. But in case you need contexthub and adding components fro...

Hi, As per sling documentation looks like synthetic components are not compatible . Pls check the below link :-  https://sling.apache.org/documentation/bundles/dynamic-includes.html#compatibility-with-components   The filter is incompatible with the following types of component: components which han...

Hi, Is SDI  working for plain resource ? Is the issue  faced only with synthetic resource or both ?   Thanks, Somen

Hi, Pls check if the "core.wcm.components.pdfviewer.v1" clientlibs are being loaded while rendering the page. PDFs will not render in case javascript is not present. Try to add clientlib using dependencies or embed property.  Thanks, Somen

Hi,  Are you able to validate the code in your local instance ?  Recommend to validate the config and then generate the same in an out folder. Later use the out folder cofigurations to start the docker and check the functionalities in local instance before deploying to cloud.    https://experiencele...

As configurations are not available , you can ignore these in refactored codebase .

Hi Prashanthi, "I can't remove or  disable replication agents as my AEM on premise is still being used. " --- During the migration process from on prem to cloud , you have to perform code refactoring . The refactored code will be residing in another branch and  on premise code should be present in e...

In case the asset is moved then old metadata value also will be shifted to other location. You have to reprocess the asset to apply the new metadata profile values. 

Hi , You can use metadata profiles to achieve the same. Pls check the below link :-   Metadata profiles | Adobe Experience Manager   Thanks, Somen

Hi,  As per the  documentaion if the max versions value is less then 1 then purging is not based on the number of versions.  So having value as 0 may be creating some conflicts and keeping the versions.   versionmanager.maxNumberVersions (int, default 5)On version purge, any version older than the ...