Search

If you look at that fifth example again, you'll see it's manipulating the data for that column, which is exactly what you want to do...

Hi @arulkumar , As @tangerine said, the error contains a link that will give you some clues. If still no joy, we're happy to take a look, but it would help, as per the forum rules, if you could link to a running test case showing the issue so we can offer some help. Information on how to create a test case (if you aren't able to link to the page you are working on) is available here. Cheers, Colin

Hi @premagopu , This example here shows how to get the row contents when clicked upon. To get the contents of the dropdown, you would probably just use jQuery to get the .val() of that node, Cheers, Colin

Thank you.I am looking now.

Yes, at the moment what happens is that the XML for the XLSX file is all created in a single "thread" (for lack of a better term - Javascript is single threaded!). The result is that there are a lot of operations to perform and that can take a long time for the browser to process. There have been some improvements in later versions, so if you are using an out of date version of the software, make sure that you update. Beyond that, there are two options: We put the XLSX generation into the background using a web worker. Server-side generation of the XLSX file. 2 offers the most flexibility, but also the harder development path, making 1 perhaps more attractive in the short term. Allan

I'm guessing this is a duplicate of this thread here.

Hi @bocahapi , This is likely to have something to do with your Ajax response. It would be worth comparing your requests and responses with the Ajax tab on this example. We're happy to take a look if you could provide a test case or link to your page. Cheers, Colin

@Allan Thanks.

Hi @ersatpal127 , Yep, that's just standard behaviour for server-side processing, see the example here, Cheers, Colin

Hi @ShahiDev , Take a look at this example here, it shows how to set the ajax.dataSrc when it isn't data. You're using sAjaxDataProp at the top-level of the initialisation, but that isn't a supported option. Cheers, Colin