Hi Manfred,

> where "data.id" is a valid property to the data of the row.
Actually, I think "id" is more valid.

CommandButton and ToolbarButton are designed to return the row property
value(s), if supplied. If not supplied, the default property for
CommandButton is "id", and the default for ToolbarButton is null (because a
toolbar button is not necessary functionally linked to selectable rows).
Please also note that it is a good practice to use an IdPropertyColumn
(like in the samples), because it automatically sets the kendo grid model
id (used for default CRUD operations).

So, in short: use "id" and an IdPropertyColumn.

Hope this helps,
Sebastien.


On Sun, Feb 19, 2017 at 12:43 PM, Martin Grigorov <martin.grigo...@gmail.com
> wrote:

> On Feb 19, 2017 10:35 AM, "Manfred Bergmann" <m...@software-by-mabe.com>
> wrote:
>
> Solved. Problem was access to the model data
>
>
> Without more details it is hard to say what is inconsistent and how it
> could be improved!
>
>
> Interestingly though that the PropertyColumn could access the data but the
> CommandButton not.
> Not sure about the internals but that's not a consistent behavior.
>
>
> Manfred
>
> --
> View this message in context: http://apache-wicket.1842946.
> n4.nabble.com/Kendo-UI-DataTable-selection-tp4677141p4677148.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
>

Reply via email to