Page 1 of 1

ActionExportReport Not Being Called

Posted: Fri Mar 07, 2014 2:29 pm
by jamesmuir
I have a simple .Net MVC 5.0 project with references to appropriate Stimulsoft libraries for the designer and the viewer. I am able to load the designer in a page and preview the report. I have a problem when I try to call the export functionality. The dialog window appears and I can make my selections but the ExportReport route is never called. My view code looks like this

Code: Select all

@Html.Stimulsoft().StiMvcDesigner(new StiMvcDesignerOptions()
{
    ActionGetReportTemplate = "GetReportTemplate",
    ActionGetReportSnapshot = "GetReportSnapshot",
    ActionExportReport = "ExportReport",
    Width = System.Web.UI.WebControls.Unit.Percentage(100),
    Height = System.Web.UI.WebControls.Unit.Pixel(700)
})
and my controller function looks like this

Code: Select all

public FileResult ExportReport()
        {
            StiReport report = StiMvcDesigner.GetReportObject(this.Request);

            return StiMvcDesigner.ExportReportResult(this.Request, report);
        }
I have verified in developer tools that the route is never being called when i click the "Ok" button in the export dialog.

I followed the documentation found here http://www.stimulsoft.com/en/documentat ... review.htm to try to accomplish this. Is there something else that is required for the export functionality to be enabled?

Re: ActionExportReport Not Being Called

Posted: Mon Mar 10, 2014 9:13 am
by HighAley
Hello.

Please, read an article from our Knowledge Base.

Thank you.

Re: ActionExportReport Not Being Called

Posted: Tue Aug 26, 2014 6:16 pm
by bschenk
I'm facing the exact same problem but I do not understand the answer to this question as it refers to an issue with Chrome.

from IE, FireFox and chrome the function "ExportReport" is never called.
Functions for ActionGetReportSnapshot and ActionEmailReport are being caller and work just fine.

Re: ActionExportReport Not Being Called

Posted: Wed Aug 27, 2014 10:13 am
by HighAley
Hello.

This error is already solved.
Please, upgrade to our latest release - 2014.1.

Thank you.