Hi @Kamal_Kishor ,There is no out-of-the-box (OOB) solution for this requirement. Since the value is dynamically generated, I assume it does not need to be displayed in the CA Config Editor.In that case, you can omit this property from the CA Config Editor definition and instead derive or compute th...

Hi @ShyamSundar ,The error appears to be related to a delay in the deactivation process. Please verify if the replication queue is blocked. Additionally, I recommend re-running the pipeline, as delays in deactivation can occasionally lead to this issue.

Hi @SivaNa3 ,Can you check if you added edit permission for the folder?.Refer the screenshot added for Google Docs 

Hi @David_Fischer92 ,Please check if this documentation helps -https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/assets-view/metadata-assets-view#metadata-forms . We can create custom metadata forms similar to schema for assets view. 

Hi @KKeerthi ,Even if your query filters by a path, adding includedPaths and excludedPaths in the AEM index definition improves performance and efficiency. includedPaths tells AEM to only index content under specific paths. excludedPaths lets you skip paths that aren’t needed. This helps in reducing...

Hi @Maikman831 ,I think includes section is missing in your path.json "includes:" [ "/content/eds-with-ue-test-by-maikman83/" ] Could you try adding this and publishing the pages?

hi @SaadAb ,Are you still facing this issue? I’ve tried the same steps in my Cloud sandbox and have not encountered any problems.When a domain is added, the system automatically checks if it’s available. If you’re seeing an error, it could be due to a service-side issue or that the domain is not ava...

There could be a syntax issue in your YAML file. Could you please debug in local using the commandaem up --print-indexRefer - https://www.aem.live/developer/indexing#debugging-your-index-configuration .When you hit the page the index properties value would be printed in your terminal.

Hi @sai_charanAr ,Raising a support ticket is recommended for these issues. However, you can try the following steps on your end:Download the pipeline logsCheck if there are any errors logged that might indicate the root cause.Re-run the pipelineSometimes the issue could be due to cloud services in ...

Hi @javed25 ,Have you tried - sling:hideChildrenRefer - https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/full-stack/sling-resource-merger#properties