Search

you can easily do this if you use the php library that accompained with datables or you have to re-invent the wheel I'm going to take field with type select as an example basically you have to define your field with type select and pass an empty array first then use field api and invoke update method. e.g editor.field('test').update(loadJson("/your/api/url")); the response from the server should be something like below your server side script should prepare the concatenated field name from your DB { label: "John Doe",value:"1" } take note loadJson is a wrapper method/function of $.ajax function to get the JSON data from the server. I hope this make sense. Please read the example carefully from the site it has a very good documentation just to start to get your feet wet. Good luck

Finding it strange that column-visibility callback does not fire when the column is hidden as a result of the responsive behavior. I assume it does not use the column().visible() API? Should it not eat its own dog food?

Hi, This will be resolved in Editor 1.5.5 which will drop tomorrow. There is a timing / async error when server-side processing is used with inline editing in 1.5.4 I'm afraid. Regards, Allan

See also the rendering section of the manual. Allan

Hi All, corrected it in the end. using the regex was the correct way. I forgot to add the draw() on the end. final code was column.search('^$',true,false).draw(); Cheers Mark

That was what I was looking for I was looking through the documentation, but somehow missed that one.. :/ Thank you :) BR Simen

There are two issues associated to scroller- 1.Loading and scrolling are pretty slower in IE unlike Chrome,Firefox which is pretty faster. 2.Blank screen with "loading.." appears in Scroller-Server Side Processing whenever we try drag and scroll using mouse. Any idea on how to enable smooth scrolling to ensure NO blank screen and "loading.." is shown whenever user tries to drag and scroll using mouse but data should be shown simulataneous to the users scroll without any delay. Any help would be highly appreciated! Thanks.

if anyone else is having the same issue refer to the stack overflow post

Yeah that is actually the road I am heading down now. I will track that in a separate branch so you can evaluate and see if you like the implementation. I also need the child row to be in the table at all times regardless if it is expanded or collapsed. Right now it is removing the child from the dom on the collapse.

Please update to the current 1.1.0 release which addresses this issue. Allan