Issue with Exporting Hierarchical Data in Gantt Chart Excel Export

[Pramod Jangra]

Hi,

I'm working on exporting filtered data from the Gantt chart using the export button click event. I want to export a custom dataSource that includes both parent and child rows, preserving the hierarchy.

Here's the relevant code snippet:

 if (args.item.id === 'GanttExport_excelexport') {

      ganttInstance.current.excelExport({

        dataSource: [

          {

            TaskID: 21,

            TaskName: 'Project initiation',

            StartDate: new Date('04/02/2024'),

            EndDate: new Date('04/21/2024'),

            Duration: 10,

            Progress: 50,

            subtasks: [

              {

                TaskID: 7,

                TaskName: 'Identify site location',

                StartDate: new Date('04/02/2024'),

                Duration: 2,

                Progress: 30,

                resources: [1],

              },

              {

                TaskID: 8,

                TaskName: 'Soil test',

                StartDate: new Date('04/03/2024'),

                Duration: 3,

                Progress: 60,

                resources: [2],

              },

            ],

          },

        ],

      });

    }



Issue:
The exported Excel file includes only one row ( TaskID:21 ) and skips the child rows ( TaskID: 7 and TaskID: 8 ), even though they are part of the subtasks array.

Expected Output:
The exported file should contain three rows—one for the parent task and two for its children—maintaining the hierarchy as displayed in the Gantt chart.

Question:
Is there an additional configuration or property required in the excelExport method to ensure that the hierarchy and child rows are included in the exported file?

Thanks in advance!

[Sridharan Jayabalan]

Hi Pramod,

 

Greetings from Syncfusion.

 

We have reviewed your query, and we are able to replicate the issue "Child records not rendering in excel export file while dynamic changes in dataSource property" in Gantt Chart.

 

To address the problem, we have logged a bug request, and the fix will be provided in the Volume 2 SP release which is scheduled to be rolled out on Mid of August. You can track its status from the feedback link given below.

 

Feedback Link - Child records not rendering in excel export file while dynamic changes in dataSource property in React | Feedback Portal

 

Disclaimer: Inclusion of this solution in the SP release may change due to other factors including but not limited to QA checks and works reprioritization.

 

 

Regards,

Sridharan

[Sridharan Jayabalan]

Pramod,

We are glad to announce that our Essential Studio ® 2025 Volume 2 SP release v30.2.4 is rolled out and is available for download under the following link.

https://www.syncfusion.com/forums/197303/essential-studio-2025-volume-2-service-pack-release-v30-2-4-is-available-for-download

The fix for the issue “Child records not rendering in excel export file while dynamic changes in dataSource property in React | Feedback Portal” has been rolled out in our Volume 2 SP Release (v30.2.4). The reported issue occurs due to using the grid's export method, only the parent record is included in the exported data. So upgrade to our latest version to resolve the problem.

Sample - 6xxrmrm4 (duplicated) - StackBlitz

We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance.

Regards,

Sridharan

[Clone 41 Job]

A frustrating issue with exporting hierarchical data in the Gantt chart! Just like navigating a tricky level in

geometry dash scratch resolving this bug will greatly enhance the user experience and streamline project management!

[Sridharan Jayabalan]

Clone 41 Job,

 

Thanks for reaching out to us.

 

We hope that the reported issue has been resolved in version 30.2.4. If you are still experiencing any problems after updating to this version, please share the details of the issue you're facing in detail so we can assist you further.

 

Looking forward to your response.

 

 

Regards,

Sridharan