Search

Hi Allan,

Sorry for adding something else to this thread, but since I just altered one of the examples given earlier, I thought I might.

Hello

var dt = new DataTable('#myTable', { "columns": [ { "data": "one" }, { "data": "two" }, ], order: [ [0,'asc'] ] });

Now at https://live.datatables.net/jemogewe/1/edit

so I'm jumping in head first again, ive worked with editor tables before but never like this...

Just set the text option for each button you need:

Thank you!

Not a bug, it doesn't bubble (that property doesn't actually appear on the rendered doc page, I'll fix that).

Dear @allan,

Its in the manual.

here is my code for the second method

here is my code for the fist method:

I suspect you are running into the issue discussed in this FAQ.

Allan, thank you for all our help. Your insights are really good and I appreciate them.

Thanks for the clarification.

Dear allan,

In addition to Allan's updated example you will need to change the selector used for the keyup event. Due to scrolling there is a cloned header used to facilitate scrolling. Using the selector #exa…

I've just recreated the issue here, based on the information provided - many thanks for that. Yes, what is happening is that the primary key value from the products table is being used and trying to …

Ah! No you are right, my apologies. The type is being added when the setup for the rendering function is run - in this case it is when the DataTable initialisation object is readied.