Skip to main content

Kendo MVC Grid DataSourceRequest with AutoMapper

Kendo Grid does not work directly with AutoMapper but could be managed by simple trick using mapping through ToDataSourceResult. The solution works fine until different filters are applied.

The problems occurs because passed filters refer to view model properties where as database model properties are required after AutoMapper is implemented.

So, the plan is to intercept DataSourceRequest  and modify names based on database model. To do that we are going to create implementation of CustomModelBinderAttribute to catch calls and have our own implementation of DataSourceRequestAttribute from Kendo MVC. I will be using same source code from Kendo but will replace column names for different criteria for sort, filters, group etc.

Let's first look into how that will be implemented.

     public ActionResult GetRoles([MyDataSourceRequest(GridId.RolesUserGrid)] DataSourceRequest request)  
     {  
       if (request == null)  
       {  
         throw new ArgumentNullException("request");  
       }  
       return Json(UnitOfWork.RoleRepository.All()  // DB Call
         .ToDataSourceResult(request, data => Mapper.Map<RoleViewModel>(data)), JsonRequestBehavior.AllowGet);  
     }  

As per above example it looks pretty simple to implement. The whole logic and idea is hidden under MyDataSourceRequest and GridId enum. MyDataSourceRequest is a direct implementation of original DataSourceRequest from Kendo MVC but with column name changes.

To know which database model is mapped to which view model. We will have enum for all AJAX grid calls and then through that we will be able to know mapped view model.

KendoHelper.cs
   /// <summary>  
     /// Grid Ids  
     /// </summary>  
     public enum GridId  
     {  
       /// <summary>  
       /// The roles user grid  
       /// </summary>  
       RolesUserGrid,  
     }  
     /// <summary>  
     /// Gets the type of the grid's AutoMapper class.  
     /// </summary>  
     /// <param name="gridId">The grid identifier.</param>  
     /// <returns></returns>  
     public static Type GetGridAutoMapperType(this GridId gridId)  
     {  
       switch (gridId)  
       {  
         case GridId.RolesUserGrid:  
           return typeof(RoleViewModel);  
       }  
       return null;  
     }  

The GetGridAutoMapperType is giving us type for the mapped class. Through this we know that GridId.RolesUserGrid is mapped to RoleViewModel class.

This is the minimum thing required to know the mapping. Now, we need two more things, the original property names by passing view model type from GetGridAutoMapperType and another function to replace view model property names with database model property names.

KendoHelper.cs
 /// <summary>  
     /// Gets the mapped property names from AutoMapper configuration.  
     /// </summary>  
     /// <param name="autoMapperType">Type of the automatic mapper.</param>  
     /// <returns></returns>  
     /// <exception cref="System.ArgumentNullException"><T>;Unable to find given type in AutoMapper.</exception>  
     public static IDictionary<string, string> GetMappedNames(Type autoMapperType)  
     {  
       if (autoMapperType == null)  
       {  
         return null;  
       }  
       var mainItem = Mapper.GetAllTypeMaps().SingleOrDefault(m => m.DestinationType.Equals(autoMapperType));  
       if (mainItem == null)  
       {  
         throw new ArgumentNullException("<T>", "Unable to find given type in AutoMapper.");  
       }  
       return (from prop in mainItem.GetPropertyMaps()  
           where prop != null &&  
           prop.DestinationProperty != null &&  
           prop.SourceMember != null &&  
           prop.DestinationProperty.Name != prop.SourceMember.Name  
           let sourceName = Convert.ToString(prop.CustomExpression.Body)  
           select new  
           {  
             DestinationPropertyName = prop.DestinationProperty.Name,  
             SourceMemberName = (sourceName != null ? sourceName.Remove(0, String.Join(String.Empty,  
             prop.CustomExpression.Parameters.Select(p => p.Name)).Length + 1) : prop.SourceMember.Name)  
           }).ToDictionary(prop => prop.DestinationPropertyName, prop => prop.SourceMemberName);  
     }  
     /// <summary>  
     /// Gets the name of the mapped property.  
     /// </summary>  
     /// <param name="value">The value.</param>  
     /// <param name="mappedProperties">The mapped properties.</param>  
     /// <param name="isReverse">if set to <c>true</c> reverse mapping.</param>  
     /// <returns>Mapped property for given value</returns>  
     public static string GetMappedName(this string value, IDictionary<string, string> mappedProperties,  
       bool isReverse = false)  
     {  
       if (String.IsNullOrEmpty(value) ||  
         mappedProperties == null || mappedProperties.Count == 0)  
       {  
         return value;  
       }  
       var mappedPropertyValue = value;  
       foreach (var mappedproperty in mappedProperties)  
       {  
         var dicKey = isReverse ? mappedproperty.Value : mappedproperty.Key;  
         var dicValue = isReverse ? mappedproperty.Key : mappedproperty.Value;  
         var regex = new Regex(String.Format(@"\b{0}\b", dicKey));  
         if (regex.IsMatch(dicKey))  
         {  
           mappedPropertyValue = regex.Replace(mappedPropertyValue, dicValue);  
         }  
       }  
       return mappedPropertyValue;  
     }  

With GetMappedNames function we can get properties names from database model and view model. The GetMappedName helper method would help us to replace string on model.

These are all helper methods we need, we can start creating attribute and own implementation of DataSourceRequest.

MyDataSourceRequestAttribute.cs
 /// <summary>  
   /// Custom data source request attribute  
   /// </summary>  
   public class MyDataSourceRequestAttribute  
     : CustomModelBinderAttribute  
   {  
     /// <summary>  
     /// Gets or sets the prefix.  
     /// </summary>  
     /// <value>  
     /// The prefix.  
     /// </value>  
     public string Prefix { get; set; }  
     /// <summary>  
     /// Gets or sets the grid identifier.  
     /// </summary>  
     /// <value>  
     /// The grid identifier.  
     /// </value>  
     public GridId? GridUniqueId { get; set; }  
     /// <summary>  
     /// Initializes a new instance of the <see cref="MyDataSourceRequestAttribute"/> class.  
     /// </summary>  
     public MyDataSourceRequestAttribute()  
     {  
     }  
     /// <summary>  
     /// Initializes a new instance of the <see cref="MyDataSourceRequestAttribute"/> class.  
     /// </summary>  
     /// <param name="gridId">The grid identifier.</param>  
     public MyDataSourceRequestAttribute(GridId gridId)  
     {  
       GridUniqueId = gridId;  
     }  
     /// <summary>  
     /// Retrieves the associated model binder.  
     /// </summary>  
     /// <returns>  
     /// A reference to an object that implements the <see cref="T:System.Web.Mvc.IModelBinder" /> interface.  
     /// </returns>  
     public override IModelBinder GetBinder()  
     {  
       var dataSourceRequestModelBinder = new MyDataSourceRequestModelBinder(GridUniqueId);  
       dataSourceRequestModelBinder.Prefix = this.Prefix;  
       return dataSourceRequestModelBinder;  
     }  
   }  

The above attribute is pretty simple takes GridId and pass it to MyDataSourceRequestModelBinder. This is the model binder which will consume our helper classes and replace property names.

MyDataSourceRequestModelBinder.cs
   /// <summary>  
   /// Custom DataSourceRequestModelBinder to handle AutoMapper mappings  
   /// </summary>  
   public class MyDataSourceRequestModelBinder  
     : IModelBinder  
   {  
     /// <summary>  
     /// Initializes a new instance of the <see cref="MyDataSourceRequestModelBinder"/> class.  
     /// </summary>  
     /// <param name="gridId">The grid identifier.</param>  
     public MyDataSourceRequestModelBinder(GridId? gridId)  
     {  
       GridUniqueId = gridId;  
     }  
     /// <summary>  
     /// Gets or sets the prefix.  
     /// </summary>  
     /// <value>  
     /// The prefix.  
     /// </value>  
     public string Prefix { get; set; }  
     /// <summary>  
     /// Gets or sets the grid identifier.  
     /// </summary>  
     /// <value>  
     /// The grid identifier.  
     /// </value>  
     public GridId? GridUniqueId { get; set; }  
     /// <summary>  
     /// Gets or sets the mapped properties.  
     /// </summary>  
     /// <value>  
     /// The mapped properties.  
     /// </value>  
     private IDictionary<string, string> MappedProperties { get; set; }  
     /// <summary>  
     /// Binds the model to a value by using the specified controller context and binding context.  
     /// </summary>  
     /// <param name="controllerContext">The controller context.</param>  
     /// <param name="bindingContext">The binding context.</param>  
     /// <returns>  
     /// The bound value.  
     /// </returns>  
     public object BindModel(ControllerContext controllerContext, ModelBindingContext bindingContext)  
     {  
       if (!GridUniqueId.HasValue)  
       {  
         DataSourceRequestModelBinder kendoDataRequestBinder = new DataSourceRequestModelBinder();  
         return kendoDataRequestBinder.BindModel(controllerContext, bindingContext);  
       }  
       MappedProperties = GridUniqueId.Value.GetMappedPropertyNames();  
       string sorts;  
       string groups;  
       string filters;  
       string aggregates;  
       int pageIndex;  
       int pageSize;  
       DataSourceRequest dataSourceRequest = new DataSourceRequest();  
       if (this.TryGetValue<string>(bindingContext, GridUrlParameters.Sort, out sorts))  
       {  
         dataSourceRequest.Sorts = GridDescriptorSerializer.  
           Deserialize<SortDescriptor>(sorts.GetMappedName(MappedProperties));  
       }  
       if (this.TryGetValue<int>(bindingContext, GridUrlParameters.Page, out pageIndex))  
       {  
         dataSourceRequest.Page = pageIndex;  
       }  
       if (this.TryGetValue<int>(bindingContext, GridUrlParameters.PageSize, out pageSize))  
       {  
         dataSourceRequest.PageSize = pageSize;  
       }  
       if (this.TryGetValue<string>(bindingContext, GridUrlParameters.Filter, out filters))  
       {  
         dataSourceRequest.Filters = FilterDescriptorFactory.Create(filters.GetMappedName(MappedProperties));  
       }  
       if (this.TryGetValue<string>(bindingContext, GridUrlParameters.Group, out groups))  
       {  
         dataSourceRequest.Groups = GridDescriptorSerializer.  
           Deserialize<GroupDescriptor>(groups.GetMappedName(MappedProperties));  
       }  
       if (this.TryGetValue<string>(bindingContext, GridUrlParameters.Aggregates, out aggregates))  
       {  
         dataSourceRequest.Aggregates = GridDescriptorSerializer.  
           Deserialize<AggregateDescriptor>(aggregates.GetMappedName(MappedProperties));  
       }  
       return dataSourceRequest;  
     }  
     /// <summary>  
     /// Tries to get the value and typecast.  
     /// </summary>  
     /// <typeparam name="T"></typeparam>  
     /// <param name="bindingContext">The binding context.</param>  
     /// <param name="key">The key.</param>  
     /// <param name="result">The result.</param>  
     /// <returns>Typecasted value</returns>  
     private bool TryGetValue<T>(ModelBindingContext bindingContext, string key, out T result)  
     {  
       if (this.Prefix.HasValue())  
       {  
         key = string.Concat(this.Prefix, "-", key);  
       }  
       ValueProviderResult value = bindingContext.ValueProvider.GetValue(key);  
       if (value == null)  
       {  
         result = default(T);  
         return false;  
       }  
       result = (T)value.ConvertTo(typeof(T));  
       return true;  
     }  
   }  

The entire source code of MyDataSourceRequestModelBinder is taken from original Kendo MVC binder. The only part that has been modified is for replacing property names by using created helper methods GridUniqueId.Value.GetMappedPropertyNames() and GetMappedName(MappedProperties) to restore it to correct value.

NOTE: This is compatible with Storing and restoring Kendo Grid state from Database. Just we need to implement described approach in it.

Update: AutoMapper Linq Projection implementation for avoiding getting all tuples from row.

Comments

Popular posts from this blog

Using Redis distributed cache in dotnet core with helper extension methods

Redis cache is out process cache provider for a distributed environment. It is popular in Azure Cloud solution, but it also has a standalone application to operate upon in case of small enterprises application. How to install Redis Cache on a local machine? Redis can be used as a local cache server too on our local machines. At first install, Chocolatey https://chocolatey.org/ , to make installation of Redis easy. Also, the version under Chocolatey supports more commands and compatible with Official Cache package from Microsoft. After Chocolatey installation hit choco install redis-64 . Once the installation is done, we can start the server by running redis-server . Distributed Cache package and registration dotnet core provides IDistributedCache interface which can be overrided with our own implementation. That is one of the beauties of dotnet core, having DI implementation at heart of framework. There is already nuget package available to override IDistributedCache i...

Trim text in MVC Core through Model Binder

Trimming text can be done on client side codes, but I believe it is most suitable on MVC Model Binder since it would be at one place on infrastructure level which would be free from any manual intervention of developer. This would allow every post request to be processed and converted to a trimmed string. Let us start by creating Model binder using Microsoft.AspNetCore.Mvc.ModelBinding; using System; using System.Threading.Tasks; public class TrimmingModelBinder : IModelBinder { private readonly IModelBinder FallbackBinder; public TrimmingModelBinder(IModelBinder fallbackBinder) { FallbackBinder = fallbackBinder ?? throw new ArgumentNullException(nameof(fallbackBinder)); } public Task BindModelAsync(ModelBindingContext bindingContext) { if (bindingContext == null) { throw new ArgumentNullException(nameof(bindingContext)); } var valueProviderResult = bindingContext.ValueProvider.GetValue(bin...

Interface based model binding to populate properties value automatically

Interface is great way to make consistency and re-useability of codes. In this tutorial, I am going to show the power of interface to populate view/domain models automatically and interchange values between models. Technologies or techniques used in this approach: - MVC. - Interface for models. - MVC model binder for associated model with interface. Through this model binder we will populate values. - T4 template to generate code to register model binder with all models associated with interface. - Generic extension method to interchange values. It might sounding bit complex to achieve small thing. Just hold on with me and see unfolding. This will result in easier maintenance and less repetitive code. First let's start with creation of Interface that need to be populate automatically. This interface would be implemented on models and values will be auto-populated on binder. /// <summary> /// Interface for storing entry related values /// </summar...

Elegantly dealing with TimeZones in MVC Core / WebApi

In any new application handling TimeZone/DateTime is mostly least priority and generally, if someone is concerned then it would be handled by using DateTime.UtcNow on codes while creating current dates and converting incoming Date to UTC to save on servers. Basically, the process is followed by saving DateTime to UTC format in a database and keep converting data to native format based on user region or single region in the application's presentation layer. The above is tedious work and have to be followed religiously. If any developer misses out the manual conversion, then that area of code/view would not work. With newer frameworks, there are flexible ways to deal/intercept incoming or outgoing calls to simplify conversion of TimeZones. These are steps/process to achieve it. 1. Central code for storing user's state about TimeZone. Also, central code for conversion logic based on TimeZones. 2. Dependency injection for the above class to ...

OpenId Authentication with AspNet Identity Core

This is a very simple trick to make AspNet Identity work with OpenId Authentication. More of all both approach is completely separate to each other, there is no any connecting point. I am using  Microsoft.AspNetCore.Authentication.OpenIdConnect  package to configure but it should work with any other. Configuring under Startup.cs with IAppBuilder app.UseCookieAuthentication(new CookieAuthenticationOptions { AuthenticationScheme = CookieAuthenticationDefaults.AuthenticationScheme, LoginPath = new PathString("/Account/Login"), CookieName = "MyProjectName", }) .UseIdentity() .UseOpenIdConnectAuthentication(new OpenIdConnectOptions { ClientId = "<AzureAdClientId>", Authority = String.Format("https://login.microsoftonline.com/{0}", "<AzureAdTenant>"), ResponseType = OpenIdConnectResponseType.IdToken, PostLogoutRedirectUri = "<my website url>", ...

Centralized model validation both for MVC/WebApi and SPA client-side validation using FluentValidation

Validation is one of the crucial parts of any application. It has to validate on both client side and server side requests. What are target features or implementation from this article? Model validation for any given model. Centralized/One code for validation on both server-side and client-side. Automatic validation of model without writing any extra codes on/under actions for validation.  NO EXTRA/ANY codes on client-side to validate any form. Compatible with SPA. Can be compatible with any client-side validation framework/library. Like Angular Reactive form validation or any jquery validation libraries. Tools used in the implementation? FluentValidation : I feel DataAnnotation validation are excellent and simple to use, but in case of complex validation or writing any custom validations are always tricker and need to write a lot of codes to achieve whereas FluentValidations are simple even in case of complex validation. Generally, we need to validate inc...

Getting started with Raspberry Pi

Raspberry Pi is a small, low powered motherboard contains 512 RAM, combined CPU and GPU. It has LAN, 2 USB, HDMI input, Audio Out, SD Card reader and S-Video connectors. We can have many Linux distribution OS on it. To configure, we just need to attach SD Card to it. SD Card could range from class 4 to class 10. In some cases Raspberry Pi could support less then class 4 cards too. It could be powered through mini USB mobile charger. Let's get started with installing OS on SD Card. There are various ways to install OS. Like we can download OSes through  http://www.raspberrypi.org/downloads  and follow the instructions given on it. There is something BerryBoot multi-boot loader through which we can have more then one OS on Raspberry Pi and boot OS according to our need.  http://www.berryterminal.com/doku.php/berryboot  instructions could be followed to install OS with very simple steps. You need to have internet connection on Raspberry Pi to install OS. It coul...

Kendo MVC Grid DataSourceRequest with AutoMapper - Advance

The actual process to make DataSourceRequest compatible with AutoMapper was explained in my previous post  Kendo MVC Grid DataSourceRequest with AutoMapper , where we had created custom model binder attribute and in that property names were changed as data models. In this post we will be looking into using AutoMapper's Queryable extension to retrieve the results based on selected columns. When  Mapper.Map<RoleViewModel>(data)  is called it retrieves all column values from table. The Queryable extension provides a way to retrieve only selected columns from table. In this particular case based on properties of  RoleViewModel . The previous approach that we implemented is perfect as far as this article ( 3 Tips for Using Telerik Data Access and AutoMapper ) is concern about performance where it states: While this functionality allows you avoid writing explicit projection in to your LINQ query it has the same fatal flaw as doing so - it prevents the qu...

Implementing/Automating audit logs in Telerik Data Access

Audit logs can be tedious task if done manually, also developer might miss to update audit log implementation on certain level. The codes would be repeated on all places if not centralized. There are many approach available to maintain change history of model/table. Like having single history table and manage all changes of all models in same table. We may maintain in same table with some flags and JSON data for change list. We will look for maintaining history table based on each required data models with minimum effort and performance. To reduce code, I am going to use T4 to generate history models automatically based on original model. Also we are going to take care of Artificial type values. Step 1 - Create a custom attribute to mark model that history need to be maintained. /// <summary> /// Attribute to maintain history table /// </summary> [AttributeUsage(AttributeTargets.Class)] public class ManageHistoryAttribute : Attribute ...