Receive a Model per parameter in a function

Question

I’m trying to get one Model in a function, which is a step view (although I don’t know if it’s possible) to then generate a list and generate a PDF.

My View:

    @model List<BDOleoTorres.Models.AutoDeclaracoesCertISCC>
    Clique <a href="@Url.Action("downloadListaISCC", "Alertas", new { modelISCC = Model })">aqui</a> para gerar lista para PDF

My controller:

public ActionResult downloadListaISCC(List<AutoDeclaracoesCertISCC> modelISCC)
{
    //Código para gerar PDF com o modelISCC recebido
    return PartialView("AlertaCertOUAPartial");
}

I get the modelISCC always without data and I do not know if what I am trying to do is possible, if not I will try to find another solution.

Answer 1

Eventually I came up with a solution that maybe not the most effective is working well. What I am doing is: I call a javascript function; I will fetch the value of the filters; I call the function (controller) to generate the PDF, sending the data of the filters; I recalculate the list and I call the PDF.

That is to say: View:

Clique <a onclick="downloadListaAlertasISCC()" style="cursor:pointer">aqui</a> para gerar lista para PDF

Function downloadListaAlertasISCC in the Javascript:

function downloadListaAlertasISCC() {
   var dataFiltro = $("#FiltrarListContrato").val();
   //Outros filtros
   window.location.href = "/Alertas/downloadListaISCC?idForn=" + dataFiltro + "";

}

Controller:

public ActionResult downloadListaISCC(DateTime? DataFimFiltro)

    //Calculo o resultado do filtros (lista)
    //Gerar a lista para PDF
    //Retornar ficheiro PDF gerado
}

Answer 2

What do I get for getting one Model in a Action is you have the representation of each property of that Model ma view and when the request to Action is made the framework of ASP.NET MVC will effect the parser fields to an instance of Model.

As you have already commented, create each field you want to move from each item in the list on view so that you can receive a List<Model> easy to manipulate in Action is something painful for the environment. Especially if you have no way to predict the size that your lists can reach.

If your list receives values typed by the user and so you need to post all the Model, then imagining as in an order screen in which each product is filled by the user, maybe post item by item is painful.

If that’s not it, if you just pass the list to the View and then just need to know what the items on that list were when it was posted to Action, then you can really solve it differently, with a list of Id s.

You at the time of setting up the view can create something like:

@model List<BDOleoTorres.Models.AutoDeclaracoesCertISCC>
...
@foreach (var I=0; I<Model.Count(); I++)
{
    <input type="hidden" id="modelId_@I" name="modelId[@I]" />
}
@* Outros campos de forma que não precisam ser postados *@
....

In his Action you get so:

public ActionResult downloadListaISCC(int[] modelId)
{
    // recupera sua lista do banco de dados 
    // processa a lista
}

That way, you’ll surely be saving resources.

If that list is about exclusions and additions in View and then it will depend on what the user will do, so it won’t be right to try to define the index of the fields to render, but to set the indexes before posting.

Example:

@model List<BDOleoTorres.Models.AutoDeclaracoesCertISCC>
...
@foreach (var I=0; I<Model.Count(); I++)
{
    <input type="hidden" id="modelId" name="modelId" />
}
@* Outros campos de forma que não precisam ser postados *@
....

Before posting, you would do something like:

$("#seuForm").submit(function () {
    var idx = 0;
    $("#modelId", this).each(function () {
        var $self = $(this);
        $self.attr("id", $self.attr("id") + "_" + idx);
        $self.attr("name", $self.attr("name") + "[" + idx + "]");
        idx++;
    });
});

This is necessary because if there is a cut in the index sequence your list will not be passed to the Model in Action completely.

Following this idea, you can add up to more than one field, for each of them you create a parameter as vector in Action, or you can opt for a ModelView, so it would look more "elegant".

Answer 3

Maybe it is more interesting to save the list of identifiers.

Something like that:

@model List<long>
    Clique <a href="@Url.Action("downloadListaISCC", "Alertas", new { ids = Model })">aqui</a> para gerar lista para PDF

And on the controller so:

public ActionResult downloadListaISCC(long[] ids)
{
    // Buscar no banco de dados pelo identificador
    //Código para gerar PDF com o modelISCC recebido
    return PartialView("AlertaCertOUAPartial");
}

Note: I have not tested, any problem comments.

Edit:

Take a look in that reference, I think it will help you.