Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Best approach to delete a large folder in aem

Avatar

Community Advisor

Hi team,

 

May I know the best approach we can use to delete a large folders in aem.

 

1. Deleting from crxde directly. Or

2. Through curl command.

 

  • Or any better approach than these two.
Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

I would not recommend either process as there might be references to other projects/pages/nodes which you might remove not knowing.

 

The best approach will be to go to Touch UI and delete it from there. You can look into deleting at a parent level folder if you would like to do it in one go. But this process will make sure all references are properly removed and no issues are observed later.

View solution in original post

3 Replies

Avatar

Level 10

Hi @Kishore_Kumar_ ,

I'm not an AEM DAM expert but I'm going to give my opinion.

Many things happen when you delete an Asset. I assume those processes are triggered by listeners on the JCR but I can't guarantee that that's the case.

For example, if you choose to delete an asset via the TouchUI, you benefit from a reference-check that makes sure you are not deleting assets that are in use. Here is an example:

theop76211228_0-1588958093539.png

If you haven't already, i strongly suggesting testing this first using the delete dialog or the References rail.

However, if you are just deciding between manual deletion in CRX DE vs deletion by cURL, it's the same thing. In both cases you will send a HTTP request to AEM to delete a node. The only difference is that in CRX DE you have the chance to change your mind before you commit XD

Avatar

Correct answer by
Employee Advisor

I would not recommend either process as there might be references to other projects/pages/nodes which you might remove not knowing.

 

The best approach will be to go to Touch UI and delete it from there. You can look into deleting at a parent level folder if you would like to do it in one go. But this process will make sure all references are properly removed and no issues are observed later.