Skip to main content

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 query result from being cached.
Since this can have a strong negative impact on the performance even though only minimal amount of data is retrieved, we advise you not to use AutoMapper projection in LINQ queries. Instead we recommend you map the instances of your persistent types after they have been completely retrieved in memory using the Map method of AutoMapper.
I am not against or in favour of any approach it all depends on requirement. If we have tables with large number of columns then it won't be good approach. So, if you plan to go with AutoMapper extension for projection then only follow ahead.

ToDataSourceResult is an extension method from Kendo, which internally takes care of projection with different sorts, filters, groups and aggregates. We need all these features except the projection that need to handled by us using AutoMapper. The ToDataSourceResult uses "Kendo.Mvc.Extensions.CreateDataSourceResult" function to form mentioned features. 

This is a only part of code that we need to implement for having AutoMapper Linq Projection:

     /// <summary>  
     /// Creates the data source result.  
     /// </summary>  
     /// <typeparam name="TModel">The type of the model.</typeparam>  
     /// <typeparam name="TResult">The type of the result.</typeparam>  
     /// <param name="queryable">The queryable.</param>  
     /// <param name="request">The request.</param>  
     /// <returns>Kendo Data source result</returns>  
     /// <remarks>MODIFICATION OF "Kendo.Mvc.Extensions.CreateDataSourceResult" TO IMPLEMENT AUTOMAPPER PROJECTION.</remarks>  
     public static DataSourceResult CreateDataSourceResult<TModel, TResult>(this IQueryable<TModel> queryable, DataSourceRequest request)  
     {  
       Func<AggregateDescriptor, IEnumerable<AggregateFunction>> aggregates = null;  
       var dataSourceResult = new DataSourceResult();  
       IQueryable queryables = queryable;  
       var filterDescriptors = new List<IFilterDescriptor>();  
       if (request.Filters != null)  
       {  
         filterDescriptors.AddRange(request.Filters);  
       }  
       if (filterDescriptors.Any<IFilterDescriptor>())  
       {  
         queryables = queryables.Where(filterDescriptors);  
       }  
       var sortDescriptors = new List<SortDescriptor>();  
       if (request.Sorts != null)  
       {  
         sortDescriptors.AddRange(request.Sorts);  
       }  
       var sortDescriptors1 = new List<SortDescriptor>();  
       var groupDescriptors = new List<GroupDescriptor>();  
       if (request.Groups != null)  
       {  
         groupDescriptors.AddRange<GroupDescriptor>(request.Groups);  
       }  
       var aggregateDescriptors1 = new List<AggregateDescriptor>();  
       if (request.Aggregates != null)  
       {  
         aggregateDescriptors1.AddRange(request.Aggregates);  
       }  
       if (aggregateDescriptors1.Any<AggregateDescriptor>())  
       {  
         IQueryable queryables1 = queryables.AsQueryable();  
         IQueryable queryables2 = queryables1;  
         if (filterDescriptors.Any<IFilterDescriptor>())  
         {  
           queryables2 = queryables1.Where(filterDescriptors);  
         }  
         dataSourceResult.AggregateResults = queryables2.Aggregate(aggregateDescriptors1.SelectMany<AggregateDescriptor, AggregateFunction>((AggregateDescriptor a) => a.Aggregates));  
         if (groupDescriptors.Any<GroupDescriptor>() && aggregateDescriptors1.Any<AggregateDescriptor>())  
         {  
           groupDescriptors.Each<GroupDescriptor>((GroupDescriptor g) =>  
           {  
             AggregateFunctionCollection aggregateFunctions = g.AggregateFunctions;  
             List<AggregateDescriptor> aggregateDescriptors = aggregateDescriptors1;  
             if (aggregates == null)  
             {  
               aggregates = (AggregateDescriptor a) => a.Aggregates;  
             }  
             aggregateFunctions.AddRange<AggregateFunction>(aggregateDescriptors.SelectMany<AggregateDescriptor, AggregateFunction>(aggregates));  
           });  
         }  
       }  
       dataSourceResult.Total = queryables.Count();  
       if (groupDescriptors.Any<GroupDescriptor>())  
       {  
         groupDescriptors.Reverse<GroupDescriptor>().Each<GroupDescriptor>((GroupDescriptor groupDescriptor) =>  
         {  
           SortDescriptor sortDescriptor3 = new SortDescriptor()  
           {  
             Member = groupDescriptor.Member,  
             SortDirection = groupDescriptor.SortDirection  
           };  
           sortDescriptors.Insert(0, sortDescriptor3);  
           sortDescriptors1.Add(sortDescriptor3);  
         });  
       }  
       if (sortDescriptors.Any<SortDescriptor>())  
       {  
         queryables = queryables.Sort(sortDescriptors);  
       }  
       IQueryable queryables3 = queryables;  
       queryables = queryables.Page(request.Page - 1, request.PageSize);  
       if (groupDescriptors.Any<GroupDescriptor>())  
       {  
         queryables = queryables.GroupBy(queryables3, groupDescriptors);  
       }  
       dataSourceResult.Data = (queryables as IQueryable<TModel>).Execute<TModel, TResult>();  
       sortDescriptors1.Each<SortDescriptor>((SortDescriptor sortDescriptor) => sortDescriptors.Remove(sortDescriptor));  
       return dataSourceResult;  
     }  
     /// <summary>  
     /// Executes the specified source.  
     /// </summary>  
     /// <typeparam name="TModel">The type of the model.</typeparam>  
     /// <typeparam name="TResult">The type of the result.</typeparam>  
     /// <param name="source">The source.</param>  
     /// <returns></returns>  
     /// <exception cref="System.ArgumentNullException">source</exception>  
     /// <remarks>MODIFICATION OF "Kendo.Mvc.Extensions.Execute" TO IMPLEMENT AUTOMAPPER PROJECTION.</remarks>  
     private static IEnumerable Execute<TModel, TResult>(this IQueryable<TModel> source)  
     {  
       if (source == null)  
       {  
         throw new ArgumentNullException("source");  
       }  
       Type elementType = source.ElementType;  
       if (elementType != typeof(AggregateFunctionsGroup))  
       {  
         return source.Project().To<TResult>();  
       }  
       // TODO: Need to test with grouping  
       List<AggregateFunctionsGroup> aggregateFunctionsGroups = new List<AggregateFunctionsGroup>();  
       foreach (AggregateFunctionsGroup aggregateFunctionsGroup in source as IQueryable)  
       {  
         var aggregateQuerable = aggregateFunctionsGroup.Items.AsQueryable() as IQueryable<TModel>;  
         if (aggregateQuerable != null)  
         {  
           aggregateFunctionsGroup.Items = aggregateQuerable.Execute<TModel, TResult>();  
           aggregateFunctionsGroups.Add(aggregateFunctionsGroup);  
         }  
       }  
       return aggregateFunctionsGroups;  
     }  

If we see above code we only have two functions but both of them are having same code as whatever Kendo is providing with very few changes. The CreateDataSourceResult function is responsible for different sorts, filters, groups and aggregates but the actual call is happening under Execute function. To implement AutoMapper Linq Projection we only needed to modify Execute function but since it is only through CreateDataSourceResult, we need to modify both.

This is return source.Project().To<TResult>(); only change done under Execute function for mapping.

NOTE: I have not tested it with grouping. Possibly that might be the reason, Kendo did not provided some kind injection for mapping.

After that being setup we only need to call in this way.

 queryable.CreateDataSourceResult<RoleDomainModel, RoleViewModel>(request)  
 // Another example
 UnitOfWork.RoleRepository.All().CreateDataSourceResult<RoleDomainModel, RoleViewModel>(request);  

If you want, we can have similar implementation like Kendo by creating our own version of extension method ToDataSourceResult which can consume our created functions.


Comments

Popular posts from this blog

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...

main method return value

Mainly we used to write "static void main" for entry point in console application. Placement of void denotes return type. In main function we could have "int" too but what does it really mean. "int main" signifies return type as integer. The return type of main function tells about execution status of application. Even if we have specified void as return type then it would be marked as successful program execution. If we mark int as return type then we are able to control the execution status. Now, what is the benefit of making main function as int. Windows OS saves result in  %ERRORLEVEL% environment variable of OS. If we create batch file and execute application through it then we will able to get status and based on result we can trigger something else through batch file. Let's suppose we have created program called TEST.EXE. Batch file script: @echo off REM Execute main program REM TEST.EXE @if  "%ERRORLEVEL%" == "0...

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...

C# Response files

Response files are similar to batch files, having some specific instruction. On execution they perform some predefined task based on instruction. Response file contains instruction to compile programs. If we have to build complex program through command line then response files are really helpful in development process. rsp is an extension for response files. By default, csc.rsp file exists under "Framework" folder Ex: C:\Windows\Microsoft.NET\Framework\v4.0.30319. csc.rsp contains long list of system references (dlls). Some contents under csc.rsp # Reference the common Framework libraries /r:Accessibility.dll /r:Microsoft.CSharp.dll /r:System.Configuration.dll /r:System.Configuration.Install.dll /r:System.Core.dll /r:System.Data.dll /r:System.Data.DataSetExtensions.dll /r:System.Data.Linq.dll .......... In same way we can have our own response file defined which might include some third party dll. Let's see an example. Suppose we have to create an appli...

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 Argume...

Making FluentValidation compatible with Swagger including Enum or fixed List support

FluentValidation is not directly compatible with Swagger API to validate models. But they do provide an interface through which we can compose Swagger validation manually. That means we look under FluentValidation validators and compose Swagger validator properties to make it compatible. More of all mapping by reading information from FluentValidation and setting it to Swagger Model Schema. These can be done on any custom validation from FluentValidation too just that proper schema property has to be available from Swagger. Custom validation from Enum/List values on FluentValidation using FluentValidation.Validators; using System.Collections.Generic; using System.Linq; using static System.String; /// <summary> /// Validator as per list of items. /// </summary> /// <seealso cref="PropertyValidator" /> public class FixedListValidator : PropertyValidator { /// <summary> /// Gets the valid items /// <...

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...

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 ...

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...