I have an Editor form that uses two "select" types for Country and Port. A port is always within a country. We have a t_able.dependeny('countryid', function(val)_ function that goes to server and requests a list of ports for that country. It then updates the portid field.
Just because is Friday and I fancied some fun after banging my head against a particularly dumb java bug, I started playing around with the form to use the new type: "datatable" on the form. I knew straight away that the format was going to be a bit wrong and would need some adjustment, but it was good enough for me to play around with on my dev instance.
Is there something I should know about using datatable as an input to a dependent function?
Thanks for pointing this out to us! I was seeing that he dependent callback didn't actually happen at all on
datatablefield types (unless you did an options update, in which case it did...). I've just corrected that, we'll unit test it (and the values) and get that into the 2.0.3 release.
Another problem with Datatable as a editing type.
With a type: "select", the default value is selected when editing. With a datatable edit field, it is not. I just trashed a number of records finding this out.
For the time being, I have reverted to just Select.
Just to complete the circle, I've sent a reply to your e-mail - hopefully we can get this resolved there.