Hi Max,

You can Vote for and Follow this request for a follow up on providing the model as context to the command column: https://feedback.telerik.com/blazor/1461283-pass-the-model-context-to-command-button. At the moment, conditional command buttons are possible in a "normal" column through the grid state, the page above shows an example. I've also added your Vote to it on your behalf to raise its priority.

Regards,
Marin Bratanov
Progress Telerik

Hello Christian,

I made a public request for this so you can Follow it. It offers a solution and some explanations on why this is not possible at the moment. Here's the link: https://feedback.telerik.com/blazor/1461283-pass-the-model-context-to-command-button

Regards,
Marin Bratanov
Progress Telerik

Hello everyone,

Most of these are now possible through the grid state from any button: https://docs.telerik.com/blazor-ui/components/grid/state

In subsequent releases we will be reviewing passing a context to the command column so you can add conditions there.

I would encourage you to take a peek at the state to see if it will suit your needs so we can discuss if anything else needs to be done.

Regards,
Marin Bratanov
Progress Telerik

Hi René,

Allowing something like that is the point of this feature request, so it's not possible at the moment. Whether it will be a method on the grid that will change the state of the rows, or allowing the context of the row to pass down to the command column is yet to be determined. The idea is to allow you to handle the command buttons like random buttons - showing and hiding them conditionally, perhaps even letting you put them in other templates.

For the time being, you could achieve something like that through a custom editing form without the built-in command buttons - either through a row template where you'll toggle the contents based on a flag (something similar is done here (in the Master-Detail section near the end) ; or through any custom edit form outside of the grid (see here and here).

Regards,
Marin Bratanov
Progress Telerik

Hello Anthony,

The priorities of various issues and enhancements depend largely on the demand and at this point new components like a scheduler and mode inputs (like combo/autocomplete) are higher on the list. At this point I can't say when this will get implemented, as it will require a non-trivial research and perhaps even a breaking change. What I can suggest is that you click the Follow button to get email notifications for status updates. We will also update the page to list the release when this will be available in once we know.

Regards,
Marin Bratanov
Progress Telerik

I renamed the item to make it more generic, because I don't know yet how would that be done best. 

Passing a "context" would require that the buttons be in a template, which is a breaking change. 

The other problem this would pose is that those buttons need to somehow be registered with the grid, and since this is now a generic RenderFragment, there is no automatic way for the grid to do that that I can see off the top of my head (this does not mean it's impossible, of course).

At the moment, I am thinking that perhaps we should extend the grid with methods that you can use to invoke the CUD operations, so you can call them from anywhere, and perhaps that would let you just use a "regular" column instead of a command column for such conditional logic.

I am going to defer to a more in-depth investigation when it is performed to decide on how this can be done best.

I agree that conditional commands would be nice to have.

Would defining the command buttons in a fashion like the snippet below suit your needs? I am asking so I get a better idea of what you would like to have and use so we can see how we could accommodate it.

If not, would you want to be able to define command buttons in the template of a column/row? If yes, how would you want to be able to define those? Would having methods on the grid like .EditItem(T myCurrentModel), .DeleteItem(T myCurrentModel), .CancelEdit(T myCurrentModel), .SaveItem(T myCurrentModel) suit your needs, so you could call them from an arbitrary place in your code?

Regards,