Reporting Modeling in ASP NET MVC

Question

I have several reports in the company, and I need to migrate them from webforms to MVC. My question is.. Do I need to create a template for each report? Is that correct? If not, how can I do?

For example:

I have a report that should list the daily movement (production) of a company warehouse employee...the data that will be returned are:

Usuário (Login no sistema):  
Nome do Usuário: 
Quantidade de requisições atendidas: 
Quantidade de itens atendidos:

Today, within my system, I have the User object, would it be interesting to model this report? Since I will only use it in this location.

Answer 1

Ideally you would create Viewmodels for your reports, but for performance and resource allocation it is best to keep queries in the database. The example you passed is a simple case and the query would not be too heavy depending on the volume.

But there may be situations where by the volume of data and the involvement of various schemas, Databases and more complex filters, you need to use views and even auxiliary tables only to store the mass generated for the display of other reports.

Particularly, even for the reports in Reportviewer, I try to keep all Datasource queries in Stored Procedures. Facilitates maintenance and reuse, in the case of migrations like yours, is half the way.

The Viewmodel for your example could be like this:

public class ProducaoViewModel {
   [Display(Name="Usuário (Login no sistema)")]
   public string LoginUsuario {get; set;}

   [Display(Name="Nome do Usuário")]
   public string NomeUsuario {get; set;}

   [Display(Name="Quantidade de requisições atendidas")]
   public int QtdRequisicoesAtendidas {get; set;} 

   [Display(Name="Quantidade de itens atendidos")]
   public int QtdItensAtendidos {get; set;}
}