filesManager_tree on the NavigationPane not updating on the newest versions of FileManager component

[Ignacy Mielniczek]

Hello,

After updating the FileManager component to the version "30.1.39", I have noticed that the "filesManager_tree" in NavigationPane is not rendering correctly or updating when new nested folders are added. I have even updated to the latest of version "32.2.7" as of today and still facing the same problem.

However, when I downgrade to the previous version of "20.3.56" the problem disappears finally.

Could you please help me with this one?

PS. I'm using Node v. "23.11.1" and Angular v. "15.2.11" in my project, and also I'm using our custom "Physical file service provider" written in Python (so far it worked fine with the previous version), which serves the files and stores in our local volume.

PS2. For your convenience, I have uploaded some screenshots.

Best Regards,

Myagmar-Erdene Purevdorj

Attachment: FileManager_error_screenshots_45bb9a27.zip

[Praveen Sellappan]

Hi Ignacy Mielniczek,

Greetings from Syncfusion Support.

We understand you are encountering an error when trying to create nested folders in the File Manager component.

To investigate the issue you described, we prepared a sample using the File Manager component and tested folder creation in the following ways:

• Using the toolbar button
• Using the context menu
• Using the public createFolder method of the File Manager component

In our testing, we created multiple levels of nested folders under a single parent folder. We performed these tests using a version later than the one you mentioned, and we did not encounter any issues during folder creation.

We have attached the sample project for your reference. Kindly review and try the folder creation steps in this sample.

If the issue still persists in your application, could you please help us by providing the following details. This will help us investigate further:

1. Confirmation that the response returned by your custom file provider includes all the required fields expected by the File Manager (especially for the folder creation operation).
2. A comparison between:
• The response format returned by our provided sample/custom provider during folder creation
• The response returned by your custom provider
3. Clear, step-by-step instructions to replicate the issue in your environment
4. A minimal reproducible sample that demonstrates the problem
   

Additionally, we have attached our documentation link that clearly explains the exact response format the File Manager component expects for each operation (including folder creation).

Documentation reference: Custom service provider in Angular File Manager | Syncfusion

Please review the documentation and the attached sample. Let us know the results or share the requested details when you have a moment. We’ll be glad to assist further.

Regards,

Praveen Sellappan

Attachment: sample_acbf8247.zip

[Ignacy Mielniczek]

Hello Praveen,

I have checked our custom provider and could not find any errors. The requests and responses sent from FileManager v.20.3.56 and v.32.2.7 look exactly the same.

I have attached the screenshots and files containing sample requests & responses which are sent and received when action "create" folder and "read folders are triggered. Could you please check if I'm missing something out?

PS. Please reload the page using CTRL + SHIFT + R to load the static files when testing. I had an experience like everything was working correctly for a moment after compiling the project with FileManager v.20.3.56 first and then using the latest version (v.32.2.7) .

Best regards,

Ignacy Mielniczek

Attachment: FileManager_v._20.3.56_and_v._32.2.7_comparison_bff867fe.zip

[Praveen Sellappan]

Hi Ignacy Mielniczek,

Thank you for the update and the attached images.

We have reviewed the details you provided and attempted to replicate the behavior using the sample previously shared. In our testing, we initially rendered one folder and then dynamically added others using the toolbar "New Folder" button, the context menu, and the createFolder public method. However, we were unable to reproduce the issue locally, even though your screenshots demonstrate it. We have attached a video showing our reproduction attempts for your reference.

To help us investigate this further, please provide the following information:

1. Review the attached video: Please confirm if the steps we followed match your workflow. If your process differs, kindly share the exact steps required to reproduce the issue.
2. Test with your provider: Connect your custom provider to the sample we previously shared. If the issue does not occur in that sample, please highlight the configuration differences between your project and our sample.
3. Test with our provider: Connect the provider we shared to your existing File Manager component. If the issue persists while using our provider, please share your full File Manager configuration code.

We look forward to your response.

Regards,

Praveen Sellappan

Attachment: filemanagerfoldercreation_ac7f542d.zip

[Ignacy Mielniczek]

Hello Praveen, 

Thank you very much for a quick response. I will look into this problem this week and I will let you know. 

Best regards,

Ignacy Mielniczek

[Praveen Sellappan]

Hi Ignacy Mielniczek,

Thank you for the update. Please let us know your findings after your review. If you need any additional information, we are here to help.

Regards,
Praveen Sellappan

[Ignacy Mielniczek]

Hello,

After inspecting I have noticed that it started to break from v. "22.1.38". Can you provide more information about "Breaking changes" or "Bug fixes" between the versions "22.1.36" and "22.1.38", please? Because I was not able to find anything on your page:

https://help.syncfusion.com/upgrade-guide/angular-ui-components?current-version=22.1.36&newer-version=22.1.38&type=BreakingChanges,BugFixes,Features,KnownIssues&includeWeeklyRelease=true

Best regards,

Ignacy Mielniczek

[Praveen Sellappan]

Hi Ignacy Mielniczek,

We have tested the sample using the latest version (v33.2.4) to reproduce the issue you mentioned. However, after multiple attempts, we were unable to replicate the reported behavior on our end.

To help us investigate this further, we kindly request you to share one of the following:

• Please try to reproduce the issue using the sample we previously shared and let us know if it still occurs.
• Alternatively, provide a minimal reproducible sample that demonstrates the issue.
• Also share a short video showing the steps to reproduce the issue.

These details will help us analyze the problem more effectively and provide you with an accurate solution.

We appreciate your cooperation and look forward to your response.

Regards,

Praveen Sellappan

[Ignacy Mielniczek]

Hello Praveen,

Thanks for a quick response. But could you please answer to my questions from the last message? I'm trying to understand what was the breaking changes between the versions "22.1.36" and "22.1.38".

Best regards,

Ignacy Mielniczek

[Praveen Sellappan]

Hi Ignacy Mielniczek,

Based on your request, please find below the release notes between versions 22.1.36 and 22.1.38 for your reference:

• Version 22.1.36 Release Notes:
  Essential Studio for Angular 2022 Weekly Nuget Release Release Notes

• Version 22.1.38 Release Notes:
  Essential Studio for Angular 2017 Weekly Nuget Release Release Notes

Additionally, we have tested the sample application in both versions (22.1.36 and 22.1.38) on our end. In both cases, we were unable to reproduce the reported issue.

We have also attached the samples created using both versions for your reference. Kindly review them and let us know if they align with your configuration or if the issue still persists.

Looking forward to your feedback.

Regards,
Praveen Sellappan

Attachment: sample_247e73a2.zip

[Ignacy Mielniczek]

Hello, 

I wanted to give you guys an update that I have resolved the issue by returning the full path to a folder or a file as "filterPath" key's value in cwd and files of our response. For example:

{
    "cwd":{
        "action":null,
        "caseSensitive":false,
        "data":null,
        "dateCreated":null,
        "dateModified":null,
        "filterId":null,
        "filterPath":" Files/test1",
        "hasChild":true,
        "id":null,
        "isFile":false,
        "name":"Files",
        "names":null,
        "newName":null,
        "parentId":null,
        "path":null,
        "permission":null,
        "previousName":null,
        "renameFiles":null,
        "searchString":null,
        "showHiddenItems":false,
        "size":0,
        "targetData":null,
        "targetPath":null,
        "type":"",
        "uploadFiles":null
    },
    "files":[
        {
            "action":null,
            "caseSensitive":false,
            "data":null,
            "dateCreated":"2026-04-23T16:13:30.734229",
            "dateModified":"2026-04-23T16:13:30.734229",
            "filterId":null,
            "filterPath":"Files/test1/test2",
            "hasChild":false,
            "id":null,
            "isFile":false,
            "name":"test",
            "names":null,
            "newName":null,
            "parentId":null,
            "path":null,
            "permission":null,
            "previousName":null,
            "renameFiles":null,
            "searchString":null,
            "showHiddenItems":false,
            "size":0,
            "targetData":null,
            "targetPath":null,
            "type":"",
            "uploadFiles":null
        }
    ],
    "details":null,
    "error":null
}

Best regards,

Ignacy Mielniczek
​

[Praveen Sellappan]

Hi Ignacy,

Thank you for the update.

We’re glad to hear that you were able to resolve the issue by returning the full path in the filterPath key for both cwd and files. That’s a great find and a helpful approach. We appreciate you sharing this solution.

If you encounter any further issues or need assistance, please feel free to reach out.

Regards,

Praveen Sellappan