Hi Manfred, PropertyColumn generates the underlying json using PropertyResolver.getValue, that's why it works. ToolbarButton and CommandButton should read directly from the json, and I didn't thought about sub-expressions. Please open an issue (and specify the version you are using). The fix is straightforward, you will be get a snapshot shortly.
Thanks & best regards, Sebastien On Sun, Feb 19, 2017 at 8:53 PM, Manfred Bergmann <m...@software-by-mabe.com> wrote: > Hi Sebastien. > > > Sebastien wrote > >> where "data.id" is a valid property to the data of the row. > > Actually, I think "id" is more valid. > > The path to by model data id is in second level. > That's why "data.id". For the PropertyColumn/IdPropertyColumn that worked > fine. > Couldn't understand thus why the CommandButton wasn't able to pull that > data. > But you explanation makes sense. > > > Sebastien wrote > > So, in short: use "id" and an IdPropertyColumn. > > Yep, doing that, thanks. > > > Manfred > > -- > View this message in context: http://apache-wicket.1842946. > n4.nabble.com/Kendo-UI-DataTable-selection-tp4677141p4677152.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
