empty fields trigger bug in columnDefs?
empty fields trigger bug in columnDefs?
Hello there.
I created some custom filters for my datatables. I used dropdowns in the header of the table. You can select a status (All, In-,Active,Pending). The filters are looking for html code in the rows.
I noticed a bug in my filter: If the table has an empty row or field the column's definition initialisation properties isn't set to type: "string".
If all fields are filled with data the column's definition initialisation properties is set correctly. Has someone a clue? I didn't found any thread about it.
Thanks.
Answers
Hi @takaest ,
We're happy to take a look, but as per the forum rules, please link to a test case - a test case that replicates the issue will ensure you'll get a quick and accurate response. 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