This documentation is for the legacy Izenda 6 product. Documentation for the new Izenda 7 product can be found at https://www.izenda.com/docs/
The AdHocContext class is used to setup the database driver, access the report set currently stored in the active user's session, and access various metrics for your license key. Below is an overview of the properties and methods available through AdHocContext and what each of them can do.
Property | Description |
---|---|
ClientLicenses | Gets the maximum number of clients supported by your current license key |
CurrentReportSet | Gets the report object that was most recently loaded by the user |
CurrentUserName | Gets the AdHocSettings.CurrentUserName property for backwards-compatibility reasons |
Driver | Gets or sets the database driver that your application will use |
ProcessorLicenses | Gets the maximum number of processors your current license key can support |
ReportSetCount | Not used internally |
SchedulerExecuting | Gets a value indicating whether the Izenda Scheduler is executing scheduled reports or not |
SetSchedulerExecuting | This method takes a boolean value that sets whether or not the Izenda Scheduler is executing |
StoreInStaticMemory | Gets or sets whether the CurrentReportSet will be stored in static memory or not |
UsersCountModel | Gets the concurrency model for your current license key |
ViewerLicenses | Gets the maximum number of users supported by your current license key |
The CurrentReportSet object is the way that Izenda exposes the most recently loaded report definition. This object can be used in many of the overrides that can be used in the Global.asax for more flexibility when dealing with saving/loading reports, modifying datasets, and displaying other useful information as your organization needs.
The Driver object is the single point of entry for all database traffic and must be set to any of the specific driver classes that Izenda provides. This will use your connection string and datasources to provide the framework for working with Izenda reports. Currently these are the types of drivers Izenda has available.
In order to set the driver for your database, you simply need to create a new driver instance and assign it to AdHocContext.
AdHocContext.Driver = new MSSQLDriver();
The default value is a new MSSQLDriver.
Note: You should refrain from using the .Driver property when working with requests to the database in custom methods, such as with ProcessDataSet. This can interfere with how Izenda works internally and cause various portions of the application to stop functioning correctly.
Normally, this setting will be automatically updated when your rs.aspx is called with the run_scheduled_reports=1 parameter. You can also update this value yourself if you need special kinds of scheduling. This can be done in PreExecuteReportSet and PostExecuteReportSet respectively.
Last edited by Michael Hornaday, 2015-11-03 11:47:18