In your demo here, the excel export includes the Hierarchical Grid (Nested Grid): http://www.igniteui.com/hierarchical-grid/export-hierarchical-grid
In my jsFiddle here, it only exports the top level: http://jsfiddle.net/phgt6gqm/7/
What did I miss?
Hi Mandeep,
Setting a responseDataKey of empty string confuses the exporter. Please remove those and exporting will work fine on all levels: http://jsfiddle.net/phgt6gqm/11/
Please let me know if you have further questions
Great. It's working now!
However, if you look at the exported file, it's missing the Headers and Data for the 2nd level nested grid.
Headers Missing: "Course Name", "Status", "Started On", "Attempts", Data Missing: "Course Name", "Started On"
Thanks for your response.
The missing headers for the 2nd grid is result of a wrong behavior, that I logged in our internal development system. In order to track this issue, I have created a new support ticket for you that is linked to the dev issue and you will receive automatic notifications on its status. You can find your active cases under Account - Support Activity in our website. Select your ticket and go to Development Issues tab to view the status of related bugs.
Please let me know what did you mean by there is missing data for "Course Name", "Started On", since I Am able to find all data under the headers exported. You can also send me a screenshot of the exported file or the exported file itself.
I am looking forward to hearing from you.
Please take a look at: http://jsfiddle.net/phgt6gqm/13/
The exported file looks like: https://snag.gy/0pbiLk.jpg
As you can see in the file, it's missing the headers (Name, Status, StartedOn)
It shows the data for Status ("not-attempted") but does not show any data for Name or Started On.
This is a critical issue for us. This is a show stopper for this project. Please suggest!
Thank you for explaining this. Actually this is also a result of the wrong behavior and as I said I have logged this in our internal system and it is pending to be fixed.
Since you say this is a critical issue for you, I will provide you with the first build that contains the fix ( around mid of January), otherwise you need to wait the official service release which is scheduled to be available in late March.
I also suggest to consider this ticket resolved and continue any discussion in the support ticket that is linked to the development issue. You can find your active cases under Account - Support Activity in our website. Select your ticket and go to Development Issues tab to view the status of related bugs.