ActiveReports 14.2 Released!

Posted by: mateen.firoz on 1 October 2020, 4:29 am EST

  • Posted 1 October 2020, 4:29 am EST

    I’m excited to announce the release of Service Pack 2 for ActiveReports 14. This service pack extends .NET Core support for section reports as well as including several fixes and enhancements. You can read all about the new features included in ActiveReports 14 here: .

    Below you will also find a list of issues that were fixed in this service pack.

    By the way, this is a free update for existing AR14 users.

    ActiveReports 14.1 Download:

    • Case: AR-24839 - Removed validation check for blank/null values for Text Delimiter property in TextExportOption.

    • Case: AR-24251 - WebViewer control does not appear in ToolBox for WebSite projects in Visual Studio 2019.

    • Case: AR-24182 - Localized StandAlone End User Report Designer to zh-cn.

    • Case: AR-24168 - Fixed FileNotFoundException on creating the new instance of PageReport in .NET Core class library.

    • Case: AR-23980 - Added support for parameters in JSON connection string in web based report designer.

    • Case: AR-23925 - Fixed issues with picture element repeating in detail section of report.

    • Case: AR-23874 - Added support for multiple datasets with custom chart controls to avoid 'DataSet name needs to be specified' error.

    • Case: AR-23730 - Exporting to JSON now retains custom DataElementName of report items.

    • Case: AR-23000 - Added ability to increase font size of 'Script' page in Visual Studio for Section, Page, and RDL reports at design time.

    • Case: AR-22741 - Simplified JSViewer API to load subreports from memory stream.

  • Replied 31 March 2021, 6:48 pm EST

    I use activereport14, based on. Net core 3.1;

    I tried to use activereport14 to return JSON data

    my code:
    public class HomeController : Controller
    public JsonResult GetJsonData(string reportName)
    PageReport report = new PageReport();
    report.Load(new FileInfo(string.Format(@"{0}/Reports/{1}.rdlx", AppContext.BaseDirectory,reportName)));
    GrapeCity.ActiveReports.Document.PageDocument reportDocument = new GrapeCity.ActiveReports.Document.PageDocument(report);

    GrapeCity.ActiveReports.Export.Text.Page.JsonRenderingExtension.Settings jsonSettings = new GrapeCity.ActiveReports.Export.Text.Page.JsonRenderingExtension.Settings();
    jsonSettings.Formatted = false;
    jsonSettings.QuotePropertyNames = true;
    GrapeCity.ActiveReports.Export.Text.Page.JsonRenderingExtension jsonRenderingExtension = new GrapeCity.ActiveReports.Export.Text.Page.JsonRenderingExtension();
    GrapeCity.ActiveReports.Rendering.IO.MemoryStreamProvider memoryProvider = new GrapeCity.ActiveReports.Rendering.IO.MemoryStreamProvider();
    reportDocument.Render(jsonRenderingExtension, memoryProvider, jsonSettings);
    var primaryStream = memoryProvider.GetPrimaryStream();
    StreamReader reader = new StreamReader(primaryStream.OpenStream());
    string readerText = reader.ReadToEnd();
    return Json(new { code = 0, msg = "success!", list = readerText });
    }catch(Exception ex){
    //Even though the program died
    //I can't grab the exception here

    My report is connected to PostgreSQL based on ODBC, and the program directly hung up during the stress test;

  • Replied 31 March 2021, 6:57 pm EST

    No source available

    Source information is missing from debug information for this module
  • Replied 31 March 2021, 6:57 pm EST

    No source available

    Source information is missing from debug information for this module
  • Replied 31 March 2021, 6:59 pm EST

    Accessing this function many times in a row will cause the program to die
  • Replied 2 April 2021, 2:28 am EST


    Can you please provide the stripped down sample so that I can replicate the issue at my end and assist your further.

  • Replied 6 April 2021, 8:11 pm EST

    I have uploaded the simplified code. This problem is accidental or not necessary. Please test it patiently many times.
    Please use the pressure test tool to perform multiple pressure tests.

    Debugging code with visual studio 2019 will reproduce the problem.

    This program is deployed to Linux server for several consecutive calls, which will cause.Net process to die.

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels