Skip to main content

Telerik MVC Grid won't refresh after delete

For a project we are using the Telerik MVC controls. I have to say that I was really pleased with the experience in general, although I had some small issues.

One of the problems I had was with the editing feature of the Telerik MVC Grid. Everything appears to work as expected except for the delete. The delete MVC action is called and the row is  deleted from the database but the grid does not refresh.

[HttpPost]
[GridAction]
public ActionResult DeleteCodetable(string codetableType, Codetable codetable)
{
_codetabelService.Delete(codetable);
//Rebind the grid
return LoadCodetable(codetableType, refreshCache: true);
}


It took me some time to find the answer on the forums. The delete action only passes the id of the element to delete to the action method. This causes some model binding validation errors as the Code and Description field are required on my Codetable object.



public class Codetable
{
[Required]
public virtual int Id { get; set; }
[Required]
public virtual string Code { get; set; }
[Required]
public virtual string Description{ get; set; }
}


By design if there are model state errors (validation didn't work) the grid is not rebound. So when the DeleteCodetable method returns the result, the grid will not refresh. I solved it by introducing the IgnoreModelErrors attribute in my code.



[HttpPost]
[IgnoreModelErrors("Code,Description"]
[GridAction]
public ActionResult DeleteCodetable(string codetableType, Codetable codetable)
{
_codetabelService.Delete(codetable);
//Rebind the grid
return LoadCodetable(codetableType, refreshCache: true);
}

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...