Hi Team, I want to upload a lot of folders with many images into AEM DAM. Thanks,Syed Peer Vali Shaik.a

Hi @BhanuMa, In AEM 6.5 (AMS), the org.apache.sling. The servlet-helpers bundle is not shipped out of the box. That’s why you don’t see it under System Console → Bundles.In AEM as a Cloud Service, the bundle is included as part of the base SDK dependencies, so your code works there without embedding...

Hi @jayv25585659, Stop AEMRemove any repo.lock file under segmentstoreEnsure port 4503 is freeStart again with: ./crx-quickstart/bin/start================================================================================When working with the AEM as a Cloud Service SDK (Quickstart), there are a couple ...

Hi @aanchal-sikka  @konstantyn_diachenko Nice information on this topic

hi @Randeep_virk Adobe’s Source Migration Tools (GitHub)The aem-cloud-service-source-migration repository includes utilities such asRepository Moderniser → restructures static templates and configurations into a Cloud-ready formatIndex Converter → converts custom Oak indexes for deployment in Cloud ...

Hi @lax50,The issue isn’t with your HTTP client code (that works fine locally), but with authentication on your Dev environment.In AEM 6.5, calling the GraphQL endpoint directly requires a valid, authorised user. Using admin: admin won’t work on non-local environments because:Admin access is usually...

Hi @Keerthi0555,Go to http://localhost:4502/libs/cq/search/content/querydebug.html============================== path → where you want to search (e.g., /content/your-site).type = nt: unstructured → components are stored as NT: unstructured nodes.property = sling:resourceType → identifies the compone...

Hi @SwathiKr3,In AEM, permissions for smart crop editing can’t be restricted directly by image profile in the user/group permissions UI. Out of the box, AEM permissions work at the folder or path level, not at the profile level.To achieve your requirement:Organise assets by image profileApply your s...

Hi @jayv25585659  A pipeline only executes one run at a time. The first merge triggers a run, and if more merges happen while that run is still in progress, they get grouped together. Once the current run finishes, the next run will pick up the newest commit on the branch.