Default Parameters without Launching Report

Default Parameters without Launching Report

Posted by: mdynna on 17 April 2026, 11:28 am EST

• 

  mdynna

  • Post Options:
  • Link
    Copy

  Posted 17 April 2026, 11:28 am EST

  We have a feature where users can build custom Page Reports that often have date parameters. We have it working where the date parameters default to some values based on a date selected earlier when the user started the application. However, this results in the report automatically running when opened. We would like the date parameters to be defaulted but still wait for the user to confirm the entry and press View Report rather than running automatically. Is this possible?

• 

  prabhat.sharma

  

  • Post Options:
  • Link
    Copy

  Posted 20 April 2026, 2:04 am EST

  Hi Mdynna,

  Thank you for reaching out to MESCIUS support.
  
  In ActiveReports.NET, when all report parameters have valid default values, the report is considered ready to execute, which causes it to run automatically when opened. This is expected behavior. Currently, there is no built-in option to keep parameter default values while preventing the report from auto-running until the user clicks View Report.

  As a workaround, you may consider the following approach:

  Leave at least one required parameter without a default value, which will prevent the report from executing automatically until the user provides or confirms the parameter value and clicks View Report.

  Please let us know if you have any further questions or need assistance.

  Regards,
  
  Prabhat Sharma.

• 

  mdynna

  • Post Options:
  • Link
    Copy

  Posted 27 April 2026, 6:52 pm EST

  Ok, that’s a bit disappointing. It would be nice if that behaviour could be turned off at the report level. I found that we can get the behaviour we want to a passable level by calling CancelRender immediately after the LoadDocument call. The report begins for a couple seconds but then stops, allowing the user to confirm or override the defaulted parameters.

• 

  prabhat.sharma

  

  • Post Options:
  • Link
    Copy

  Posted 28 April 2026, 3:49 am EST

  Hi Mdynna,

  Thank you for sharing your approach.

  Sorry for the inconvenience caused. We understand your requirement and have tested the suggested method of calling CancelRender() immediately after LoadDocument(). Although it interrupts the rendering process, we observed that the report still enters the rendering state before cancellation occurs. As a result, the parameter UI becomes non-editable, and the viewer may display a blank or grey screen after rendering is stopped.
  
  Since this approach appears to be working in your environment, we request that you share a stripped-down, reproducible sample (with dummy data) or modify the attached sample to demonstrate the behavior and revert to us. This will help us investigate the scenario more effectively and validate whether the approach is reliable and suitable for broader use.

  Additionally, we are discussing this behavior with our development team to further review this behavior and explore if there is a better or more reliable workaround available.
  
  [Internal Tracking ID: AR-37413]

  Regards,
  
  Prabhat Sharma.

• 

  mdynna

  • Post Options:
  • Link
    Copy

  Posted 28 April 2026, 10:55 am EST

  Yes, we are also added these lines to display the parameters window:
  
  ARViewer.Sidebar.Visible = True
  
  ARViewer.Sidebar.SelectedIndex = 3

• 

  prabhat.sharma

  

  • Post Options:
  • Link
    Copy

  Posted 28 April 2026, 11:41 pm EST

  Hi Mdynna,

  We’re glad to hear that you were able to find a workaround. The developer has recommended the same workaround for now.
  
  The feature request has been acknowledged and added to their research backlog, though there is no ETA available currently.

  Please feel free to reach out if you have any questions or need further assistance.

  Regards,
  
  Prabhat Sharma.