Last Updated: 26 Oct 2020 07:55 by ADMIN
Created on: 02 Apr 2020 15:19
Category: FileManager
Type: Feature Request
Improve the files/folders moving process in the FileManager. Create a relation between the Create and Destroy methods

Currently, if we move files/folders from one folder to another, the FileManager sends two requests to the backend - Create and Destroy. The Create method is called to "create"  the files in their new destination and the Destroy method removes the files from their previous location. 

The two methods are executed independently and the results from each of them don't affect the result of the other. There are scenarios in which when we move files, the Create call can fail or be prevented because of limited user rights, but the Destroy method will be executed resulting in files' deletion. The same is applicable in scenarios where the Destroy is unsuccessful. 

It will be a very useful FileManager feature if there is a relation in the Create and Destroy methods' execution.


Posted on: 26 Oct 2020 07:55

Hello, Greg,

As you can see, the issue that my colleague referenced is now resolved and closed. In addition, I would suggest referring to the new command event in our documentation, where the status of the commands could be revised: 

Hope this would help.

Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at

Posted on: 21 Jul 2020 13:51

Hi Nigel,

Indeed, the lack of such relation between the two requests may result in deleting a file, if Create fails and Destroy succeeds, or file duplication, if Create succeeds and Destroy fails. We will take the following issue into consideration for FileManager improvements.

Progress Telerik

Posted on: 15 Jul 2020 06:16

I have found this functionality to be a critical bug in the FileManager. Using the demo page here I've been able to replicate the loss of files. Steps are simply:

  • Create a new folder inside the Images folder
  • Drag the 10 images into this new folder
  • Drag them back
  • Repeat

Almost immediately, you will find there's no longer 10 images as the Create routine fails to complete before the Destroy routine is initiated resulting in 1 or more files being lost.

This is not so much a feature request as a critical bug.